List all active DoorDash carts
AI agents call list_carts 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 queries and retrieves information about existing shopping carts without creating, modifying, deleting, or executing any actions. It is a read-only operation with minimal security risk—an AI agent listing carts cannot cause financial transactions, data destruction, or unintended side effects beyond information disclosure.
From the tool's definition Tool name 'list_carts' and description 'List all active DoorDash carts' indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
List all active DoorDash carts. 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 list_carts: 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.
list_carts 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 list_carts 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 list_carts. 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.
list_carts 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 →