Get order status, total, and line items for an order id (e.g. ORD-5002).
AI agents call get_order 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 queries order data without side effects. It performs a read-only lookup of existing order information (status, total, line items) based on an order identifier. There is no data modification, deletion, code execution, or financial transaction involved. It is a straightforward Read operation with minimal risk if misused by an AI agent.
From the tool's definition Tool description states it 'Get[s] order status, total, and line items for an order id' — purely retrieval operations with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
Get order status, total, and line items for an order id (e.g. ORD-5002). 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 get_order: 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.
get_order 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_order 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_order. 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_order 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 →