get_order_details
AI agents call get_order_details to retrieve information from Qanat Goose MCP Extension without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name and position among order management tools (get_catalog_items, get_recent_orders, mark_order_complete, process_refund, toggle_item_status) clearly indicate this retrieves order details without side effects. No creation, modification, deletion, or financial transaction occurs—it only queries and returns existing data.
From the tool's definition Tool name 'get_order_details' indicates a retrieval operation. Server context shows order management functions where this tool retrieves order information (consistent with sibling tools like 'get_recent_orders').
Attacks that exploit this kind of access
get_order_details. It is categorised as a Read tool in the Qanat Goose MCP Extension MCP Server, which means it retrieves data without modifying state.
Register the Qanat Goose MCP Extension 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 Qanat Goose MCP Extension. 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 Qanat Goose MCP Extension MCP server (professordnyc/qanat-goose-mcp). 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 →