Query application traces and logs
AI agents call azure_traces to retrieve information from MCP Container Tools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Although querying logs may expose sensitive data (application internals, user activity, secrets if logged), the operation itself is purely informational and does not modify, delete, or execute code. Severity is medium because log access can reveal sensitive information useful for reconnaissance or privilege escalation, but the tool itself performs no destructive or code-execution actions.
From the tool's definition Tool description states 'Query application traces and logs' — a retrieval operation with no side effects. The verb 'query' and context of reading logs and traces confirm read-only semantics.
Attacks that exploit this kind of access
Query application traces and logs. It is categorised as a Read tool in the MCP Container Tools MCP Server, which means it retrieves data without modifying state.
Register the MCP Container Tools MCP server in PolicyLayer and add a rule for azure_traces: 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 MCP Container Tools. Nothing to install.
azure_traces 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 azure_traces 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 azure_traces. 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.
azure_traces is provided by the MCP Container Tools MCP server (simseksem/mcp-container-tools). 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 →