Get orders history for a user. Optionally filter by year (e.g., 2025, 2024). Set onlyUnreturned to true to exclude returned/refunded items.
AI agents call get-orders-history to retrieve information from Shopping MCP Server (Amazon + Target) 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 existing order data without creating, modifying, deleting, or executing operations. It has no side effects beyond reading historical transaction information. While the data retrieved may be sensitive (purchase history), the low blast radius of read-only access and lack of operational impact justifies a 'low' severity classification.
From the tool's definition Tool retrieves order history data with optional filtering by year and return status. The description uses 'Get' and 'retrieve' language indicating data fetching with no modification or deletion capabilities.
Attacks that exploit this kind of access
Get orders history for a user. Optionally filter by year (e.g., 2025, 2024). Set onlyUnreturned to true to exclude returned/refunded items. It is categorised as a Read tool in the Shopping MCP Server (Amazon + Target) MCP Server, which means it retrieves data without modifying state.
Register the Shopping MCP Server (Amazon + Target) MCP server in PolicyLayer and add a rule for get-orders-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 Shopping MCP Server (Amazon + Target). Nothing to install.
get-orders-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 get-orders-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 get-orders-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.
get-orders-history is provided by the Shopping MCP Server (Amazon + Target) MCP server (sachinparyani/mcp-server-shopping). 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 →