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.
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.
Attacks that exploit this kind of access
The rule that runs bridge_addChainToWallet safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 0xaibridge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bridge_addChainToWallet, this is the rule to start with:
bridge_addChainToWallet stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 0xaibridge, apply this rule, and every bridge_addChainToWallet call is checked against it from then on.
Questions about 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. 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.
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.
bridge_addChainToWallet is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
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.
This server
Across the catalogue