List all orders for a customer, newest first.
AI agents call list_customer_orders to retrieve information from Acme Operations Assistant without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays existing order information for a customer without creating, modifying, deleting, or executing any side effects. It is a straightforward read operation typical of customer support systems. Severity is low because misuse would only expose customer order history data, not enable destructive or financial actions.
From the tool's definition Tool name 'list_customer_orders' and description 'List all orders for a customer, newest first' indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
List all orders for a customer, newest first. It is categorised as a Read tool in the Acme Operations Assistant MCP Server, which means it retrieves data without modifying state.
Register the Acme Operations Assistant MCP server in PolicyLayer and add a rule for list_customer_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 Acme Operations Assistant. Nothing to install.
list_customer_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 list_customer_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 list_customer_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.
list_customer_orders is provided by the Acme Operations Assistant MCP server (yesidevelop/simple-mcp-server). 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 →