Poll for events (stopped, continued, terminated). Use after launch/step.
AI agents call debug_poll_events to retrieve information from Polybugger without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the status of a debugging session by polling for event updates. It has no side effects—it merely retrieves state information about whether a debugged process has stopped, continued, or terminated. It does not execute code, modify data, or trigger external operations. This is a pure read operation on debug session state.
From the tool's definition Tool name 'debug_poll_events' and description 'Poll for events (stopped, continued, terminated)' indicate a retrieval operation that queries the current state of a debug session without modifying or executing code.
Attacks that exploit this kind of access
Poll for events (stopped, continued, terminated). Use after launch/step. It is categorised as a Read tool in the Polybugger MCP Server, which means it retrieves data without modifying state.
Register the Polybugger MCP server in PolicyLayer and add a rule for debug_poll_events: 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 Polybugger. Nothing to install.
debug_poll_events 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_poll_events 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_poll_events. 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_poll_events is provided by the Polybugger MCP server (wilfoa/polybugger-mcp). 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 →