open_context
AI agents call open_context to retrieve information from Debug Companion MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'open_context' combined with the server's stated capability of 'displaying code context around failures' suggests this tool reads and displays code snippets around error locations. The description is empty, which lowers confidence. Classified as Read since it most likely retrieves file content for display, with medium severity because it could expose source code.
From the tool's definition Tool name 'open_context' and server description mentions 'displaying code context around failures' — likely reads/displays source code context.
Attacks that exploit this kind of access
open_context. It is categorised as a Read tool in the Debug Companion MCP MCP Server, which means it retrieves data without modifying state.
Register the Debug Companion MCP server in PolicyLayer and add a rule for open_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 Debug Companion MCP. Nothing to install.
open_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 open_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 open_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.
open_context is provided by the Debug Companion MCP server (shanirap/mcp-server). 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 →