Get order history from Minted
AI agents call get_minted_orders to retrieve information from Minted MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves past order information, which is a read-only query operation. However, the medium severity reflects that order history may contain sensitive personal financial information (order amounts, items, dates, and delivery details) that could be exploited if exposed to an unauthorized agent. The confidence is high because the intent is unambiguously to fetch existing data without side effects.
From the tool's definition Tool name 'get_minted_orders' and description 'Get order history from Minted' indicate retrieval of historical order data with no modification capability. Server description confirms this is for 'retrieve...order history' operations.
Attacks that exploit this kind of access
Get order history from Minted. It is categorised as a Read tool in the Minted MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Minted MCP Server MCP server in PolicyLayer and add a rule for get_minted_orders: 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 Minted MCP Server. Nothing to install.
get_minted_orders 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_minted_orders 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_minted_orders. 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_minted_orders is provided by the Minted MCP Server MCP server (markmhendrickson/mcp-server-minted). 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 →