Long-poll for the next qualifying workflow event. The server manages the sequence cursor internally. Returns { event } when an event arrives, or { event: null } after ~60s if none arrives. Re-call immediately either way — no arguments needed.
AI agents call get-next-event to retrieve information from Mmc without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool is a polling/retrieval mechanism that reads events from the server's internal event bus without modifying state, executing code, or triggering external operations. Even though it is part of a workflow sequencing system, the tool itself is purely observational—it fetches and returns event data. The 'no arguments needed' design further confirms it is a passive read operation.
From the tool's definition Tool description states it 'Long-poll for the next qualifying workflow event' and 'Returns { event }'. The tool retrieves/queries event data from an internal event bus with no side effects.
Attacks that exploit this kind of access
Long-poll for the next qualifying workflow event. The server manages the sequence cursor internally. Returns { event } when an event arrives, or { event: null } after ~60s if none arrives. Re-call immediately either way — no arguments needed. It is categorised as a Read tool in the Mmc MCP Server, which means it retrieves data without modifying state.
Register the Mmc MCP server in PolicyLayer and add a rule for get-next-event: 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 Mmc. Nothing to install.
get-next-event 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-next-event 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-next-event. 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-next-event is provided by the Mmc MCP server (modelmycontext/mmc-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 →