razz_cancel_queue
Cancel your pending spectator crash queue entry. Only works if you are queued (not if already playing in a live round). Use get_my_queue first to check your status.
This record as markdown: /tools/io-github-razz-games-razz/razz-cancel-queue.md
What razz_cancel_queue does on Razz Games
AI agents use razz_cancel_queue to create or update resources in Razz Games, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Razz Games environment.
Why razz_cancel_queue is rated Medium
This tool cancels a pending queue entry, which is a reversible write/modification action (removing a queue reservation). It does not delete permanent data, execute code, or directly move funds — the queue entry is simply removed before a game round begins. Since it only affects a pending queue state (not an active wager or completed transaction), it falls under Write rather than Destructive or Financial.
From the tool's definition Cancel your pending spectator crash queue entry. Only works if you are queued (not if already playing in a live round).
Attacks that exploit this kind of access
The rule that runs razz_cancel_queue safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Razz Games, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For razz_cancel_queue, this is the rule to start with:
razz_cancel_queue stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Razz Games, apply this rule, and every razz_cancel_queue call is checked against it from then on.
Questions about razz_cancel_queue
Cancel your pending spectator crash queue entry. Only works if you are queued (not if already playing in a live round). Use get_my_queue first to check your status. It is categorised as a Write tool in the Razz Games MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Razz Games MCP server in PolicyLayer and add a rule for razz_cancel_queue: 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 Razz Games. Nothing to install.
razz_cancel_queue is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the razz_cancel_queue 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 razz_cancel_queue. 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.
razz_cancel_queue is provided by the Razz Games MCP server (@razzgames/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Razz Games, and thousands of servers like it.
This server
Across the catalogue