create_snipe · Restaurant Reservation MCP Server MCP

WHAT IT DOES

What create_snipe does on Restaurant Reservation MCP Server

AI agents invoke create_snipe to trigger actions in Restaurant Reservation MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why create_snipe needs a policy

This tool triggers an automated external operation that will execute a booking action autonomously the moment a slot becomes available. It is not merely writing a record — it sets in motion a persistent, autonomous process that interacts with external reservation platforms (Resy/OpenTable) and commits a reservation on the user's behalf without further human approval.

From the tool's definition 'Schedule an automatic reservation snipe. The sniper will book instantly when slots open.'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_snipe Rate-limited

create_snipe stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_snipe": {
      "limits": [
        {
          "counter": "create_snipe_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Restaurant Reservation MCP Server, so you can run agents against it safely.

FAQ

Questions about create_snipe

What does the create_snipe tool do? +

Schedule an automatic reservation snipe. The sniper will book instantly when slots open. EXAMPLES: - Simple: create_snipe(restaurantId: 12345, restaurantName:. It is categorised as a Execute tool in the Restaurant Reservation MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on create_snipe? +

Register the Restaurant Reservation MCP Server MCP server in PolicyLayer and add a rule for create_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.

What risk level is create_snipe? +

create_snipe is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit create_snipe? +

Yes. Add a rate_limit block to the create_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.

How do I block create_snipe completely? +

Set action: deny in the PolicyLayer policy for create_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.

What MCP server provides create_snipe? +

create_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.