Get recent DoorDash order history
AI agents call order_history to retrieve information from DoorDash MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical data about past orders. It performs a read-only query operation with no ability to modify, delete, or execute actions. The data returned is informational only, and misuse by an AI agent would result in unauthorized access to order information rather than financial or operational harm.
From the tool's definition Tool name 'order_history' and description 'Get recent DoorDash order history' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get recent DoorDash order history. It is categorised as a Read tool in the DoorDash MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DoorDash MCP Server MCP server in PolicyLayer and add a rule for order_history: 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 DoorDash MCP Server. Nothing to install.
order_history 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 order_history 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 order_history. 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.
order_history is provided by the DoorDash MCP Server MCP server (spunkysarb/doordash-mcp). 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 →