Get line items (entries) for an order. Returns products, quantities, prices.
AI agents call get_order_items to retrieve information from Kaspi Merchant 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 line item data (products, quantities, prices) without creating, modifying, deleting, or executing any operations. It is a straightforward read operation. Although the server operates on production data, the tool itself poses minimal risk as it only fetches information for display or analysis purposes.
From the tool's definition Tool name 'get_order_items' and description 'Get line items (entries) for an order. Returns products, quantities, prices' indicate a retrieval-only operation with no modification or side effects.
Attacks that exploit this kind of access
Get line items (entries) for an order. Returns products, quantities, prices. It is categorised as a Read tool in the Kaspi Merchant MCP Server, which means it retrieves data without modifying state.
Register the Kaspi Merchant MCP server in PolicyLayer and add a rule for get_order_items: 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 Kaspi Merchant. Nothing to install.
get_order_items 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_items 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_items. 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_items is provided by the Kaspi Merchant MCP server (theyahia/kaspi-merchant-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 →