Get orders by customer ID
AI agents call get_orders_by_customer_id to retrieve information from E-commerce 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 order information for a given customer ID. It has no side effects—it does not create, modify, delete, or execute operations. The operation is a simple data query against test data. Even if an AI agent misuses this tool by querying multiple customer IDs, the blast radius is limited to information disclosure, which is a low-severity read risk.
From the tool's definition Tool name 'get_orders' and description 'Get orders by customer ID' indicate a retrieval operation. Server description explicitly states the interface 'query e-commerce data' with 'test data', confirming read-only intent.
Attacks that exploit this kind of access
Get orders by customer ID. It is categorised as a Read tool in the E-commerce MCP Server MCP Server, which means it retrieves data without modifying state.
Register the E-commerce MCP Server MCP server in PolicyLayer and add a rule for get_orders_by_customer_id: 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 E-commerce MCP Server. Nothing to install.
get_orders_by_customer_id 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_by_customer_id 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_by_customer_id. 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_by_customer_id is provided by the E-commerce MCP Server MCP server (kodymullins/mcp_test). 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 →