check_cart_issues

THE RISK

Low Risk

Why check_cart_issues needs a policy

This tool retrieves and queries cart data to identify unavailable items and suggest alternatives. It performs no reversible modifications (Write), executions (Execute), irreversible deletions (Destructive), or financial operations (Financial).

From the tool's definition Tool checks cart contents and lists information about product availability and substitutes without modifying cart state. Verbs 'checks' and 'lists' indicate read-only operations. No cart modifications, deletions, or side effects are performed.

Documented attack patterns abuse exactly the kind of access check_cart_issues gives an agent:

POLICY

How to control check_cart_issues

PolicyLayer is an MCP gateway — it sits between your AI agents and Frisco MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for check_cart_issues:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_cart_issues": {}
  }
}

check_cart_issues is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Frisco MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Frisco MCP tools

Financial finish_session Opens the browser at the checkout page so you can select a delivery time and pay. Destructive clear_cart Empties the Frisco cart using the site Destructive clear_session Clears the saved session and closes the browser. Destructive remove_item_from_cart Removes a specific product from the Frisco cart by name (partial match supported). Execute login Opens a visible Chromium browser to log in to Frisco manually. Run this first to establish Write add_items_to_cart Adds products to cart by selecting from the most recent search_products result page. No ad Write update_item_quantity Changes the quantity of a product already in the cart (partial name match supported). Read get_logs Returns persisted JSONL log events for the current or selected session.

All 15 Frisco MCP tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about check_cart_issues

What does the check_cart_issues tool do? +

Checks the cart for sold-out or unavailable products and lists available substitutes for each. It is categorised as a Read tool in the Frisco MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_cart_issues? +

Register the Frisco MCP server in PolicyLayer and add a rule for check_cart_issues: 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 Frisco MCP. Nothing to install.

What risk level is check_cart_issues? +

check_cart_issues is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit check_cart_issues? +

Yes. Add a rate_limit block to the check_cart_issues 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.

How do I block check_cart_issues completely? +

Set action: deny in the PolicyLayer policy for check_cart_issues. 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.

What MCP server provides check_cart_issues? +

check_cart_issues is provided by the Frisco MCP server (mkidawa/frisco-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Frisco MCP tool call.

Start from Frisco MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →