AI agents call wait to retrieve information from Scopa without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool only waits/polls for a game state condition (whose turn it is) and returns status information. It has no side effects, does not modify data, and does not trigger any external operations. It is purely a synchronization/read operation.
From the tool's definition Block until it is your turn to play. Returns immediately if it already is.
Attacks that exploit this kind of access
Block until it is your turn to play. Returns immediately if it already is. It is categorised as a Read tool in the Scopa MCP Server, which means it retrieves data without modifying state.
Register the Scopa MCP server in PolicyLayer and add a rule for wait: 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 Scopa. Nothing to install.
wait 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 wait 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 wait. 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.
wait is provided by the Scopa MCP server (seboostian02/scopa-mcp-server). 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 →