fix: fix the HR scenario issue by implementing the tools filtering and updated azure.yaml

[Dhruvkumar-Microsoft]

Purpose

This pull request updates configuration and code to improve domain-specific tool access and deployment instructions. The main changes are the introduction of per-domain tool whitelisting for the MCP server, updating the logic to connect agents to domain-specific endpoints, and clarifying deployment steps in azure.yaml.

Domain-specific tool access and routing:

• Expanded the DOMAIN_ALLOWED_TOOLS mapping in mcp_config.py to specify which tools are available for each domain (e.g., hr, tech_support, marketing, product, image). This ensures that each domain only exposes the relevant tools to the LLM and reduces the risk of cross-domain tool confusion.
• Updated the from_env method in MCPConfig to rewrite the MCP server base URL to the domain-scoped endpoint (e.g., /hr/mcp), so each agent connects to its domain’s dedicated endpoint. The client-side allowed_tools filter remains as a safety net.

Deployment instructions:

• Improved clarity of post-provisioning steps in azure.yaml by numbering the Bash and PowerShell commands as "STEP 1" and "STEP 2" to make the deployment process easier to follow. [1] [2] [3]
• Commented out the metadata block in azure.yaml (was previously active).

Does this introduce a breaking change?

• Yes
• No

How to Test

• Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

• Test the code

What to Check

Verify that the following are valid

• ...

Other Information