High Risk →

commerce_preflight

Run preflight checks before a purchase. Validates passport, delegation, merchant, and spend limits.

How to control commerce_preflight ↓

What commerce_preflight does on Agent Passport System — Cryptographic Identity for AI Agents

AI agents invoke commerce_preflight to trigger actions in Agent Passport System — Cryptographic Identity for AI Agents. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

ParameterTypeRequiredDescription
amount number Yes Purchase amount
agent_id string Yes Agent making the purchase
currency string Currency code
delegation_id string Yes Commerce delegation ID
merchant_name string Yes Merchant to purchase from

Parameters from the server's own tool schema.

High Risk

Why commerce_preflight needs a policy

Although this is a validation/check operation rather than moving money directly, it 'runs' checks (Execute verb) and directly gates financial operations (purchases). The tool validates passports, delegation chains, and spend limits—all critical controls for financial transactions. Misuse could allow an AI agent to bypass purchase safeguards or validate fraudulent transactions.

From the tool's definition 'Run preflight checks before a purchase' indicates the tool executes validation logic that determines whether a purchase can proceed. This is an executable operation that triggers external validation logic and could enable or block financial transactions.

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

How to control commerce_preflight

PolicyLayer is an MCP gateway — it sits between your AI agents and Agent Passport System — Cryptographic Identity for AI Agents, and nothing reaches the server without passing your rules. This is the rule we recommend for commerce_preflight:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "commerce_preflight": {
      "limits": [
        {
          "counter": "commerce_preflight_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

commerce_preflight stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Agent Passport System — Cryptographic Identity for AI Agents — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about commerce_preflight

What does the commerce_preflight tool do? +

Run preflight checks before a purchase. Validates passport, delegation, merchant, and spend limits. It is categorised as a Execute tool in the Agent Passport System — Cryptographic Identity for AI Agents MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does commerce_preflight accept? +

commerce_preflight accepts 5 parameters: amount, agent_id, currency, delegation_id, merchant_name. Required: amount, agent_id, delegation_id, merchant_name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on commerce_preflight? +

Register the Agent Passport System — Cryptographic Identity for AI Agents MCP server in PolicyLayer and add a rule for commerce_preflight: 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 Agent Passport System — Cryptographic Identity for AI Agents. Nothing to install.

What risk level is commerce_preflight? +

commerce_preflight is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit commerce_preflight? +

Yes. Add a rate_limit block to the commerce_preflight 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 commerce_preflight completely? +

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

commerce_preflight is provided by the Agent Passport System — Cryptographic Identity for AI Agents MCP server (https://mcp.aeoess.com/sse). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Agent Passport System — Cryptographic Identity for AI Agents tool call.

Start from Agent Passport System — Cryptographic Identity for AI Agents, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

150 Agent Passport System — Cryptographic Identity for AI Agents tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.