Get the current context snapshot for a run.
AI agents call get_current_context_snapshot to retrieve information from State Trace without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves state information from a working memory system without altering, executing code, or performing destructive operations. It is a pure read operation that queries existing data. The low severity reflects that misuse would only expose internal state information without enabling further harmful actions through this tool alone.
From the tool's definition Tool name is 'get_current_context_snapshot' and description states 'Get the current context snapshot for a run.' The verb 'Get' indicates retrieval of data with no modification or side effects.
Attacks that exploit this kind of access
Get the current context snapshot for a run. It is categorised as a Read tool in the State Trace MCP Server, which means it retrieves data without modifying state.
Register the State Trace MCP server in PolicyLayer and add a rule for get_current_context_snapshot: 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 State Trace. Nothing to install.
get_current_context_snapshot 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_current_context_snapshot 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_current_context_snapshot. 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_current_context_snapshot is provided by the State Trace MCP server (agent-pattern-labs/state-trace). 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 →