Retrieve all orders for a specific customer by name.
AI agents call get_orders_by_customer_name to retrieve information from MCP GraphQL Sales Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward read operation querying sales order data. It has no side effects—it only retrieves existing information from the database. The blast radius of misuse is minimal: an agent could retrieve customer order history, but cannot modify, delete, or execute financial transactions with this tool alone.
From the tool's definition Tool retrieves order data by customer name ('Retrieve all orders for a specific customer by name'). No modification, deletion, or execution of external operations described. Purely a data retrieval operation.
Attacks that exploit this kind of access
Retrieve all orders for a specific customer by name. It is categorised as a Read tool in the MCP GraphQL Sales Server MCP Server, which means it retrieves data without modifying state.
Register the MCP GraphQL Sales Server MCP server in PolicyLayer and add a rule for get_orders_by_customer_name: 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 MCP GraphQL Sales Server. Nothing to install.
get_orders_by_customer_name 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_name 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_name. 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_name is provided by the MCP GraphQL Sales Server MCP server (jambelg/mcp-graphql-claude). 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 →