path402_connect_wallet

Connect an external wallet provider (e.g. Metanet/Babbage) to the agent. This allows real payments to be made using the user

Category Financial
Risk class Critical
Parameters 00 required

What path402_connect_wallet does on Path402 — Tokenised Web Content for AI Agents

AI agents use path402_connect_wallet to commit financial operations through Path402 — Tokenised Web Content for AI Agents — usually the final step of a payment, billing, or trading workflow. A call moves real money.

Why path402_connect_wallet needs a policy

This tool connects a wallet to the agent, enabling real financial transactions. Once connected, the agent gains the ability to authorize payments on behalf of the user, making it a financial risk. The direct enablement of real payments justifies the Financial category with high severity, as a misuse could lead to unauthorized spending.

From the tool's definition Connect an external wallet provider...This allows real payments to be made using the user

Questions about path402_connect_wallet

What does the path402_connect_wallet tool do? +

Connect an external wallet provider (e.g. Metanet/Babbage) to the agent. This allows real payments to be made using the user. It is categorised as a Financial tool in the Path402 — Tokenised Web Content for AI Agents MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on path402_connect_wallet? +

Register the Path402 — Tokenised Web Content for AI Agents MCP server in PolicyLayer and add a rule for path402_connect_wallet: 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 Path402 — Tokenised Web Content for AI Agents. Nothing to install.

What risk level is path402_connect_wallet? +

path402_connect_wallet is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit path402_connect_wallet? +

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

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

path402_connect_wallet is provided by the Path402 — Tokenised Web Content for AI Agents MCP server (path402). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.