query_sampled_traces
AI agents call query_sampled_traces to retrieve information from AWS Application Signals MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries existing trace data for diagnostic purposes. Querying traces is a read operation with no side effects—it observes and analyzes application behavior without creating, modifying, deleting, or executing anything. Low severity because exposure is limited to visibility into traced transactions (a monitoring concern, not operational impact).
From the tool's definition Tool name 'query_sampled_traces' and server description indicate querying/retrieving distributed tracing data from AWS X-Ray. The name uses 'query' (a read operation) and 'traces' (observability/monitoring data).
Attacks that exploit this kind of access
query_sampled_traces. It is categorised as a Read tool in the AWS Application Signals MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AWS Application Signals MCP Server MCP server in PolicyLayer and add a rule for query_sampled_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 AWS Application Signals MCP Server. Nothing to install.
query_sampled_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 query_sampled_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 query_sampled_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.
query_sampled_traces is provided by the AWS Application Signals MCP Server MCP server (mxiamxia/appsignals-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 →