Get details about a specific order.
AI agents call get_order_details 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 without modifying, deleting, or executing external operations. It is a straightforward data query with no side effects, fitting the Read category. Severity is low because exposure of order details, while potentially sensitive, does not directly enable financial transactions, data destruction, or code execution—it is informational only.
From the tool's definition Tool name 'get_order_details' and description 'Get details about a specific order' indicate a retrieval operation. The server description states it 'Provides tools to query e-commerce data' with no mention of modification or deletion.
Attacks that exploit this kind of access
Get details about a specific order. 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_order_details: 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_order_details 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_details 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_details. 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_details 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 →