Retrieves Azure environment context. TYPES: subscriptions, resource_groups, resources, custom (KQL) CACHING: 5min default, bypass_cache=true for fresh data EXAMPLES: - Find VMs: custom_query =
AI agents call get_azure_context to retrieve information from Azure Omni-Tool MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and retrieves information about Azure resources and environment state. It supports listing subscriptions, resource groups, and resources, as well as custom read-only KQL (Kusto Query Language) queries. There is no capability to modify, delete, or execute operations—only to fetch and inspect existing data. The caching mechanism further confirms read-only semantics.
From the tool's definition Tool name 'get_azure_context' and description 'Retrieves Azure environment context' explicitly indicate a retrieval operation.
Attacks that exploit this kind of access
Retrieves Azure environment context. TYPES: subscriptions, resource_groups, resources, custom (KQL) CACHING: 5min default, bypass_cache=true for fresh data EXAMPLES: - Find VMs: custom_query =. It is categorised as a Read tool in the Azure Omni-Tool MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Azure Omni-Tool MCP Server MCP server in PolicyLayer and add a rule for get_azure_context: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Azure Omni-Tool MCP Server. Nothing to install.
get_azure_context is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_azure_context rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for get_azure_context. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
get_azure_context is provided by the Azure Omni-Tool MCP Server MCP server (vedantparmar12/azure-_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →