Get shipping cost estimates for items in the cart.
AI agents call shipping_estimate 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 |
|---|---|---|---|
city_id | number | Yes | Destination city ID |
Parameters from the server's own tool schema.
This tool retrieves shipping cost information based on current cart contents. It performs no side effects, creates no orders, modifies no data, and executes no external operations. It is a straightforward read/query operation similar to other retrieval tools on this e-commerce platform (get_cart, get_orders, get_product_details).
From the tool's definition Tool name 'shipping_estimate' and description 'Get shipping cost estimates' indicate data retrieval only. The verb 'get' and 'estimates' confirm this is a query operation that returns information without modifying cart state, orders, or other data.
Attacks that exploit this kind of access
Get shipping cost estimates for items in the cart. It is categorised as a Read tool in the Perkakasku MCP Server, which means it retrieves data without modifying state.
shipping_estimate accepts 1 parameter: city_id. Required: city_id. 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 shipping_estimate: 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.
shipping_estimate 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 shipping_estimate 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 shipping_estimate. 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.
shipping_estimate 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 →