返回当前 MCP 进程的运行上下文，用于排查 Trae 或沙箱环境差异。
AI agents call debug_runtime_context to retrieve information from ArcGIS Pro Bridge MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a diagnostic/inspection tool that queries and returns information about the current runtime environment. It exhibits Read characteristics: retrieval of system state information with no side effects. The tool is intended for troubleshooting and visibility into the execution context.
From the tool's definition Tool returns/retrieves current MCP process runtime context for debugging purposes (Chinese description: '返回当前 MCP 进程的运行上下文，用于排查 Trae 或沙箱环境差异' = 'returns current MCP process runtime context for troubleshooting Trae or sandbox environment differences').
Documented attack patterns abuse exactly the kind of access debug_runtime_context gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ArcGIS Pro Bridge MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for debug_runtime_context:
{
"version": "1",
"default": "deny",
"tools": {
"debug_runtime_context": {}
}
}debug_runtime_context 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.
返回当前 MCP 进程的运行上下文，用于排查 Trae 或沙箱环境差异。. It is categorised as a Read tool in the ArcGIS Pro Bridge MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ArcGIS Pro Bridge MCP Server MCP server in PolicyLayer and add a rule for debug_runtime_context: 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 ArcGIS Pro Bridge MCP Server. Nothing to install.
debug_runtime_context 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_runtime_context 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_runtime_context. 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_runtime_context is provided by the ArcGIS Pro Bridge MCP Server MCP server (sangwxx/arcgis-pro-bridge-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 13 ArcGIS Pro Bridge MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
13 ArcGIS Pro Bridge MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.