Poll pending UI events from a plugin on a client. Events are drained on read.
AI agents call plugin_get_events to retrieve information from Overlord MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The primary action is reading/polling events (Read category), but the tool has a notable side effect: events are irreversibly drained/consumed from the queue upon access. While this is technically a state modification, it is a consequence of the read operation itself rather than the tool's primary purpose. The tool does not create, modify, execute code, delete data, or move money.
From the tool's definition Tool description states 'Poll pending UI events from a plugin on a client' with events being 'drained on read', indicating retrieval of data with a side effect of consuming/clearing the event queue.
Attacks that exploit this kind of access
Poll pending UI events from a plugin on a client. Events are drained on read. It is categorised as a Read tool in the Overlord MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Overlord MCP Server MCP server in PolicyLayer and add a rule for plugin_get_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 Overlord MCP Server. Nothing to install.
plugin_get_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 plugin_get_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 plugin_get_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.
plugin_get_events is provided by the Overlord MCP Server MCP server (skeeminator/overlord-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 →