Get the order history from a user's Doordash account (remote zen).
AI agents call get_orders_with_pagination to retrieve information from Get Gather 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 without modifying, deleting, or executing transactions. It falls under the Read category. Severity is high because order history is sensitive personal and financial information—an AI misusing this could expose detailed purchase patterns, addresses, vendor preferences, and inferred financial behavior.
From the tool's definition Tool name is 'get_orders_with_pagination' and description states 'Get the order history from a user's Doordash account'. The verb 'Get' and retrieval-only operation indicate no data modification, deletion, or financial transactions.
Documented attack patterns abuse exactly the kind of access get_orders_with_pagination gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Get Gather, and nothing reaches the server without passing your rules. This is the rule we recommend for get_orders_with_pagination:
{
"version": "1",
"default": "deny",
"tools": {
"get_orders_with_pagination": {}
}
}get_orders_with_pagination is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the order history from a user's Doordash account (remote zen). It is categorised as a Read tool in the Get Gather MCP Server, which means it retrieves data without modifying state.
Register the Get Gather MCP server in PolicyLayer and add a rule for get_orders_with_pagination: 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 Get Gather. Nothing to install.
get_orders_with_pagination 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_orders_with_pagination 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_orders_with_pagination. 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_orders_with_pagination is provided by the Get Gather MCP server (remotebrowser/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 62 Get Gather tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
62 Get Gather tools catalogued and risk-classified — across an index of 42,500+ MCP servers.