Bridge an existing ONFT (LayerZero-enabled NFT) from the current Abstract chain to another L0 chain ID. FEATURES • Uses sendFrom – will move token ID cross-chain • Destination address defaults to sender but can be overridden / ENS • Requires user to have prepaid fees on source chain (value=0 by d...
AI agents invoke ab_bridge_nft to trigger actions in Society Abstract MCP. 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.
This tool triggers a cross-chain transaction that moves an NFT from one blockchain to another via LayerZero. It executes an on-chain operation (sendFrom) with real financial/asset consequences.
From the tool's definition Bridge an existing ONFT (LayerZero-enabled NFT) from the current Abstract chain to another L0 chain ID. Uses sendFrom – will move token ID cross-chain.
Attacks that exploit this kind of access
Bridge an existing ONFT (LayerZero-enabled NFT) from the current Abstract chain to another L0 chain ID. FEATURES • Uses sendFrom – will move token ID cross-chain • Destination address defaults to sender but can be overridden / ENS • Requires user to have prepaid fees on source chain (value=0 by default) COMMON SCENARIOS • Cross-chain game asset migration • Demonstrations of ONFT technology in workshops • Moving NFTs from testnet to mainnet collections. It is categorised as a Execute tool in the Society Abstract MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Society Abstract MCP server in PolicyLayer and add a rule for ab_bridge_nft: 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 Society Abstract MCP. Nothing to install.
ab_bridge_nft is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the ab_bridge_nft 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 ab_bridge_nft. 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.
ab_bridge_nft is provided by the Society Abstract MCP server (wearesociety/abstract_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →