New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

bridge_addChainToWallet

Get the OxaChain L1 chain configuration formatted as EIP-3085 wallet_addEthereumChain params. Return this to the agent so it (or the dApp) can add OxaChain L1 to a wallet like MetaMask.

SERVER0xaibridge SOURCE@0xaibridge/mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/0xaibridge-mcp/bridge-addchaintowallet.md

What bridge_addChainToWallet does on 0xaibridge

AI agents use bridge_addChainToWallet to create or update resources in 0xaibridge, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 0xaibridge environment.

Why bridge_addChainToWallet is rated Medium

An AI agent can call bridge_addChainToWallet faster than any human can review: one bad instruction and it creates or modifies resources in 0xaibridge by the hundred, each call as confident as the last.

Questions about bridge_addChainToWallet

What does the bridge_addChainToWallet tool do? +

Get the OxaChain L1 chain configuration formatted as EIP-3085 wallet_addEthereumChain params. Return this to the agent so it (or the dApp) can add OxaChain L1 to a wallet like MetaMask. It is categorised as a Write tool in the 0xaibridge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on bridge_addChainToWallet? +

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

What risk level is bridge_addChainToWallet? +

bridge_addChainToWallet is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit bridge_addChainToWallet? +

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

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

bridge_addChainToWallet is provided by the 0xaibridge MCP server (@0xaibridge/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on 0xaibridge, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of 0xaibridge's. Pull the full record:

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.