Debug tool to inspect MCP context and user mapping information
AI agents call debug_context_info to retrieve information from Open Paper Trading MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool is a diagnostic/introspection utility that reads context and user mapping data. It has no side effects—it does not modify data, execute operations, delete anything, or commit financial transactions. The 'inspect' verb confirms read-only behavior.
From the tool's definition Tool name 'debug_context_info' and description 'Debug tool to inspect MCP context and user mapping information' indicate it retrieves/queries internal state information without modification or execution of external operations.
Documented attack patterns abuse exactly the kind of access debug_context_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Open Paper Trading MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for debug_context_info:
{
"version": "1",
"default": "deny",
"tools": {
"debug_context_info": {}
}
}debug_context_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Debug tool to inspect MCP context and user mapping information. It is categorised as a Read tool in the Open Paper Trading MCP MCP Server, which means it retrieves data without modifying state.
Register the Open Paper Trading MCP server in PolicyLayer and add a rule for debug_context_info: 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 Open Paper Trading MCP. Nothing to install.
debug_context_info 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 debug_context_info 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 debug_context_info. 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.
debug_context_info is provided by the Open Paper Trading MCP server (open-agent-tools/open-paper-trading-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Open Paper Trading MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
44 Open Paper Trading MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.