Find nearby Burger King locations by address or ZIP code. Returns location names, addresses, and hours.
AI agents call find_locations to retrieve information from Burger King MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a geographic lookup that retrieves restaurant information without modifying, executing operations, or incurring financial obligations. It is a straightforward Read operation with minimal risk to the user or business.
From the tool's definition Tool description states it 'Find[s] nearby Burger King locations by address or ZIP code. Returns location names, addresses, and hours.' This is a pure retrieval operation with no side effects—it queries and returns publicly available location data.
Attacks that exploit this kind of access
Find nearby Burger King locations by address or ZIP code. Returns location names, addresses, and hours. It is categorised as a Read tool in the Burger King MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Burger King MCP Server MCP server in PolicyLayer and add a rule for find_locations: 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 Burger King MCP Server. Nothing to install.
find_locations 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 find_locations 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 find_locations. 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.
find_locations is provided by the Burger King MCP Server MCP server (markswendsen-code/mcp-burgerking). 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 →