Get detailed information about a specific Shake Shack location by ID.
AI agents call get_location_details 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 and queries location information without creating, modifying, or deleting any data. It is a pure read operation that has no impact on the restaurant's systems or business operations. The low severity reflects minimal risk even if an AI agent were to misuse it—it would only expose publicly available location details.
From the tool's definition Tool name 'get_location_details' and description 'Get detailed information about a specific Shake Shack location by ID' indicate retrieval of location data with no side effects or modifications.
Attacks that exploit this kind of access
Get detailed information about a specific Shake Shack location by ID. 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_location_details: 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_location_details 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_location_details 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_location_details. 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_location_details 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 →