List saved queries
AI agents call list_saved_queries to retrieve information from Azure Log Analytics MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about previously saved queries within an Azure Log Analytics workspace. It performs a pure read operation—listing existing resources without creating, modifying, deleting, or executing anything. Even if an AI agent misuses this tool, the exposure is limited to discovering what queries exist in the workspace, which is informational only.
From the tool's definition Tool name 'list_saved_queries' and description 'List saved queries' indicate a retrieval/query operation with no data modification.
Attacks that exploit this kind of access
List saved queries. It is categorised as a Read tool in the Azure Log Analytics MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Azure Log Analytics MCP Server MCP server in PolicyLayer and add a rule for list_saved_queries: 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 Log Analytics MCP Server. Nothing to install.
list_saved_queries 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 list_saved_queries 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 list_saved_queries. 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.
list_saved_queries is provided by the Azure Log Analytics MCP Server MCP server (rasta26/azure_log_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 →