Cancel a scheduled snipe attempt.
AI agents call cancel_snipe to permanently remove resources in Restaurant Reservation MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cancelling a scheduled snipe permanently removes/terminates the automated reservation snipe task. This action is irreversible — once cancelled, the snipe configuration is gone and cannot be restored. It falls under Destructive as it irreversibly deletes a scheduled operation. Severity is medium since the blast radius is limited to losing a reservation attempt rather than financial loss or data corruption.
From the tool's definition Cancel a scheduled snipe attempt
Attacks that exploit this kind of access
Cancel a scheduled snipe attempt. It is categorised as a Destructive tool in the Restaurant Reservation MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Restaurant Reservation MCP Server MCP server in PolicyLayer and add a rule for cancel_snipe: 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 Restaurant Reservation MCP Server. Nothing to install.
cancel_snipe is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the cancel_snipe 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 cancel_snipe. 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.
cancel_snipe is provided by the Restaurant Reservation MCP Server MCP server (jrklein343-svg/restaurant-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 →