Browse the Wingstop menu. Returns items with name, description, price, calories, available flavors, and sizes. Optionally filter by category.
AI agents call get_menu 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 performs a read-only query of menu data. It retrieves and displays information (name, description, price, calories, flavors, sizes) without creating, modifying, deleting, or executing any actions. The optional category filter is still a retrieval operation. No financial transaction or destructive action occurs.
From the tool's definition Tool description states it 'Browse[s] the Wingstop menu' and 'Returns items' - purely a retrieval operation with no modifications or side effects.
Attacks that exploit this kind of access
Browse the Wingstop menu. Returns items with name, description, price, calories, available flavors, and sizes. Optionally filter by category. 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 get_menu: 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.
get_menu 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_menu 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_menu. 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_menu 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 →