Poll for events sent from the live game client via the WebSocket bridge. Returns and clears all queued events. Event types: item_ctrl_clicked (user Ctrl/Cmd+clicked an item — payload has roomItemId), location_selected (user Shift+clicked a location — payload has position data). Call after connect...
AI agents call poll_game_events to retrieve information from Portals without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a polling/retrieval operation on queued events from the game client. It has no side effects beyond clearing the queue after reading, which is a standard pattern for event consumption. The user interactions themselves originate from the game client, not from this tool. It does not create, modify, delete, or execute operations — it only reads. Therefore, it is classified as Read with low severity.
From the tool's definition Tool description states it "Poll for events" and "Returns and clears all queued events." The function retrieves event data from a WebSocket bridge without modifying game state or executing operations — it only reads user interaction events (item clicks,…
Attacks that exploit this kind of access
Poll for events sent from the live game client via the WebSocket bridge. Returns and clears all queued events. Event types: item_ctrl_clicked (user Ctrl/Cmd+clicked an item — payload has roomItemId), location_selected (user Shift+clicked a location — payload has position data). Call after connect_to_game, after set_room_data/apply_operations, and whenever the user says they interacted with the game. It is categorised as a Read tool in the Portals MCP Server, which means it retrieves data without modifying state.
Register the Portals MCP server in PolicyLayer and add a rule for poll_game_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 Portals. Nothing to install.
poll_game_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 poll_game_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 poll_game_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.
poll_game_events is provided by the Portals MCP server (portals-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 →