Get trace entries with pagination.
AI agents call get_trace to retrieve information from MCPEmulate without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The get_trace tool retrieves trace entries from an emulation session, which is a read-only operation. It has no side effects, does not execute code, does not modify state, and does not delete data. While the broader emulation server provides Execute-class tools (like assemble, create_emulator), this specific tool is purely informational.
From the tool's definition Tool name is 'get_trace' and description states 'Get trace entries with pagination' – this is a retrieval operation that queries existing trace data without modifying or executing code.
Attacks that exploit this kind of access
Get trace entries with pagination. It is categorised as a Read tool in the MCPEmulate MCP Server, which means it retrieves data without modifying state.
Register the MCPEmulate MCP server in PolicyLayer and add a rule for get_trace: 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 MCPEmulate. Nothing to install.
get_trace 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_trace 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_trace. 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_trace is provided by the MCPEmulate MCP server (labguy94/mcpemulate). 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 →