AI agents call get_order_history to retrieve information from Rohlik without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Maximum number of orders to return (1-100, default: 10) |
Parameters from the server's own tool schema.
This tool retrieves and queries past order information without creating, modifying, deleting, or executing any operations. It is a straightforward read operation on user account history. The severity is low because accessing historical order data poses minimal risk even if misused by an AI agent—it cannot affect current operations, finances, or system state.
From the tool's definition Tool name 'get_order_history' and description 'Get your past delivered orders' indicate retrieval of historical data with no modification or side effects.
Attacks that exploit this kind of access
Get your past delivered orders. It is categorised as a Read tool in the Rohlik MCP Server, which means it retrieves data without modifying state.
get_order_history accepts 1 parameter: limit. The full parameter table on this page comes from the server's own tool schema.
Register the Rohlik MCP server in PolicyLayer and add a rule for get_order_history: 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 Rohlik. Nothing to install.
get_order_history 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_history 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_history. 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_history is provided by the Rohlik MCP server (@tomaspavlin/rohlik-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 →