Get details about a specific snipe by ID.
AI agents call get_snipe to retrieve information from Restaurant Reservation MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about an existing snipe configuration without creating, modifying, or deleting any data. It is a query operation that returns details based on an ID parameter. While the broader server context includes automated reservation 'sniper' functionality that could have financial implications, this specific tool only reads snipe details and performs no write, execute, or destructive actions.
From the tool's definition Tool name is 'get_snipe' and description states 'Get details about a specific snipe by ID' — a retrieval operation with no side effects or modifications.
Attacks that exploit this kind of access
Get details about a specific snipe by ID. It is categorised as a Read tool in the Restaurant Reservation MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Restaurant Reservation MCP Server MCP server in PolicyLayer and add a rule for get_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.
get_snipe 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 get_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 get_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.
get_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 →