Start a new order at a selected Wingstop location. Must be called before adding items. Use find_locations to get a location ID.
AI agents use create_order to create or update resources in Mcp Wingstop — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Wingstop environment.
This tool creates a new order, which is a reversible state change (orders can be cancelled or discarded before checkout). It does not execute arbitrary code, delete data irreversibly, or move money.
From the tool's definition Tool description states 'Start a new order' which creates a new order record. Combined with sibling tools like 'add_item', 'apply_coupon', 'checkout', and 'remove_item', this is clearly part of an order management workflow that modifies state in the Wingstop…
Attacks that exploit this kind of access
Start a new order at a selected Wingstop location. Must be called before adding items. Use find_locations to get a location ID. It is categorised as a Write tool in the Mcp Wingstop MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Wingstop MCP server in PolicyLayer and add a rule for create_order: 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.
create_order is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_order 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 create_order. 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.
create_order 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 →