Low Risk

detect_checkout

Scan the active browser tab for a payment form. Returns which fields were found (card number, CVV, expiry, name). Requires the AgentPay Chrome extension.

Part of the Agentpay MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call detect_checkout to retrieve information from Agentpay 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 detect_checkout 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.

agentpay.yaml
tools:
  detect_checkout:
    rules:
      - action: allow

See the full Agentpay policy for all 17 tools.

Tool Name detect_checkout
Category Read
MCP Server Agentpay MCP Server
Risk Level Low

View all 17 tools →

Agents calling read-class tools like detect_checkout have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the detect_checkout tool do? +

Scan the active browser tab for a payment form. Returns which fields were found (card number, CVV, expiry, name). Requires the AgentPay Chrome extension.. It is categorised as a Read tool in the Agentpay MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on detect_checkout? +

Add a rule in your Intercept YAML policy under the tools section for detect_checkout. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Agentpay MCP server.

What risk level is detect_checkout? +

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

Can I rate-limit detect_checkout? +

Yes. Add a rate_limit block to the detect_checkout rule in your Intercept 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 detect_checkout completely? +

Set action: deny in the Intercept policy for detect_checkout. 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 detect_checkout? +

detect_checkout is provided by the Agentpay MCP server (agentpay-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Agentpay

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.