List the caller's aggregated multi-merchant cart, grouped by shop_domain by default. The cart is auto-created on first call so iOS/web UIs always have a stable id for the cart-icon badge (matches REST GET behaviour). Identity resolved from Authorization: Bearer <jwt> or X-Curie-Device-Id header. ...
Part of the Curie Commerce server.
Free to start. No card required.
AI agents call curie_cart_aggregate_get to retrieve information from Curie Commerce without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though curie_cart_aggregate_get only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"curie_cart_aggregate_get": {}
}
}See the full Curie Commerce policy for all 29 tools.
These attack patterns abuse exactly the kind of access curie_cart_aggregate_get gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
List the caller's aggregated multi-merchant cart, grouped by shop_domain by default. The cart is auto-created on first call so iOS/web UIs always have a stable id for the cart-icon badge (matches REST GET behaviour). Identity resolved from Authorization: Bearer <jwt> or X-Curie-Device-Id header. Optional shop_domain filter returns the flat lines for a single shop. Returns { cart_id, shops, total_cents, currency_code, line_count } — the same envelope the REST GET emits so iOS + web render identical numbers.. It is categorised as a Read tool in the Curie Commerce MCP Server, which means it retrieves data without modifying state.
Register the Curie Commerce MCP server in PolicyLayer and add a rule for curie_cart_aggregate_get: 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 Curie Commerce. Nothing to install.
curie_cart_aggregate_get 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 curie_cart_aggregate_get 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 curie_cart_aggregate_get. 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.
curie_cart_aggregate_get is provided by the Curie Commerce MCP server (https://chat.curie.app/api/mcp/global). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 29 Curie Commerce tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.