Get a store
AI agents call get_store_menu 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 returns store menu information with no side effects. It does not create, modify, delete, or execute any operations—it purely retrieves data. The sibling tools (add_to_cart, remove_from_cart, order_history, etc.) confirm this is a read-only data retrieval function. Confidence is high despite the terse description, as the tool's purpose is unambiguous within the DoorDash context.
From the tool's definition Tool name 'get_store_menu' and description 'Get a store' indicate a retrieval operation. Within the context of a DoorDash MCP server, this retrieves menu data from a restaurant/store without modifying any data.
Attacks that exploit this kind of access
Get a store. 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 get_store_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 DoorDash MCP Server. Nothing to install.
get_store_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_store_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_store_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_store_menu 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 →