Get order history from Target.com. Optionally filter by year (e.g., 2025, 2024) and order type (online, instore, or both). Returns orders with essential details: order number, date, total, and items.
AI agents call get-target-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 retrieves and queries existing order history data without side effects. It does not create, modify, delete, or execute operations. While it accesses potentially sensitive personal financial transaction history, the tool itself performs only data retrieval.
From the tool's definition Tool description states 'Get order history from Target.com' and 'Returns orders with essential details'. The verb 'Get' and the read-only nature of retrieving historical order data indicate no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Get order history from Target.com. Optionally filter by year (e.g., 2025, 2024) and order type (online, instore, or both). Returns orders with essential details: order number, date, total, and 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-target-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-target-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-target-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-target-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-target-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 →