AI agents call get_context to retrieve information from Pwno without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to retrieve debugger context information within a stateful debugging session. With no description provided, confidence is moderate. In a debugging context, retrieving state (registers, memory, breakpoints, etc.) is a read operation with minimal blast radius if misused by an agent.
From the tool's definition Tool name 'get_context' suggests retrieval of debugging context/state. Description is empty; inferred from naming convention and server purpose (debugging system). Likely queries current debugger state without modifying it.
Documented attack patterns abuse exactly the kind of access get_context gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pwno, and nothing reaches the server without passing your rules. This is the rule we recommend for get_context:
{
"version": "1",
"default": "deny",
"tools": {
"get_context": {}
}
}get_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.
get_context. It is categorised as a Read tool in the Pwno MCP Server, which means it retrieves data without modifying state.
Register the Pwno MCP server in PolicyLayer and add a rule for get_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 Pwno. Nothing to install.
get_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 get_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 get_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.
get_context is provided by the Pwno MCP server (pwno-io/pwno-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 36 Pwno tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
36 Pwno tools catalogued and risk-classified — across an index of 42,500+ MCP servers.