Get information about how to order at Shake Shack (app, kiosk, online, etc.).
AI agents call get_ordering_info to retrieve information from Mcp Shakeshack without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves static information about Shake Shack's ordering channels and processes. It has no side effects, does not modify data, execute code, or perform financial transactions. It is purely informational and therefore classified as Read with low severity, as misuse would only result in the AI agent presenting ordering information to users—a benign outcome.
From the tool's definition Tool name 'get_ordering_info' and description state it retrieves information about ordering methods (app, kiosk, online, etc.). No modification, deletion, or execution of commands is indicated. It is a passive information retrieval operation.
Attacks that exploit this kind of access
Get information about how to order at Shake Shack (app, kiosk, online, etc.). It is categorised as a Read tool in the Mcp Shakeshack MCP Server, which means it retrieves data without modifying state.
Register the Mcp Shakeshack MCP server in PolicyLayer and add a rule for get_ordering_info: 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 Mcp Shakeshack. Nothing to install.
get_ordering_info 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_ordering_info 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_ordering_info. 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_ordering_info is provided by the Mcp Shakeshack MCP server (markswendsen-code/mcp-shakeshack). 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 →