Find nearby Wingstop restaurant locations. Returns address, hours, phone, distance, and delivery availability.
AI agents call find_locations to retrieve information from Mcp Wingstop without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries restaurant location information and returns static data about nearby establishments. There are no side effects, no data modification, no code execution, and no financial implications. It is a straightforward read operation similar to a search or list function.
From the tool's definition Tool 'find_locations' retrieves restaurant location data (address, hours, phone, distance, delivery availability) with no modification or execution of operations. It is purely informational—a search/query function.
Attacks that exploit this kind of access
Find nearby Wingstop restaurant locations. Returns address, hours, phone, distance, and delivery availability. It is categorised as a Read tool in the Mcp Wingstop MCP Server, which means it retrieves data without modifying state.
Register the Mcp Wingstop 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 Mcp Wingstop. 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 Mcp Wingstop MCP server (markswendsen-code/mcp-wingstop). 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 →