List the 20 most recent orders for the logged-in user, or get full detail for a specific order by invoice number.
AI agents call get_orders to retrieve information from Perkakasku without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
noinv | string | — | Invoice number (e.g. 'INV2503001'). Omit to list recent orders. |
status | string | — | Filter by status code. O=Waiting confirmation, B=Waiting payment, C=Customer confirmed, P=In process, S=Partial delivery, K=Delivered, D=Received, T=Cancelled. |
Parameters from the server's own tool schema.
This tool purely retrieves order history and details for the logged-in user. It queries existing data without creating, modifying, deleting, or executing any operations. While it provides access to potentially sensitive order information, the retrieval-only nature classifies it as Read with low severity, as misuse would only expose data rather than cause operational or financial damage.
From the tool's definition Tool description states 'List the 20 most recent orders' and 'get full detail for a specific order' — these are retrieval operations with no modification or side effects.
Attacks that exploit this kind of access
List the 20 most recent orders for the logged-in user, or get full detail for a specific order by invoice number. It is categorised as a Read tool in the Perkakasku MCP Server, which means it retrieves data without modifying state.
get_orders accepts 2 parameters: noinv, status. The full parameter table on this page comes from the server's own tool schema.
Register the Perkakasku MCP server in PolicyLayer and add a rule for get_orders: 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 Perkakasku. Nothing to install.
get_orders 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 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. 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 is provided by the Perkakasku MCP server (perkakasku-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 →