sponsor_bridge_fee
AI agents use sponsor_bridge_fee to commit financial operations through Tenzro Ledger MCP — usually the final step of a payment, billing, or trading workflow. A call moves real money.
The name strongly suggests a financial operation: 'sponsor' implies paying on behalf of someone, and 'bridge_fee' refers to fees for cross-chain bridge transactions. Given the server's explicit mention of payments and bridges, this is most likely a Financial action. Confidence is moderate because the description is empty, leaving some ambiguity about exact behavior.
From the tool's definition Tool name 'sponsor_bridge_fee' combined with server context mentioning 'payments, bridges' — sponsoring a bridge fee implies committing financial resources to cover cross-chain transaction costs.
Attacks that exploit this kind of access
sponsor_bridge_fee. It is categorised as a Financial tool in the Tenzro Ledger MCP MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Tenzro Ledger MCP server in PolicyLayer and add a rule for sponsor_bridge_fee: 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 Tenzro Ledger MCP. Nothing to install.
sponsor_bridge_fee is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the sponsor_bridge_fee 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 sponsor_bridge_fee. 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.
sponsor_bridge_fee is provided by the Tenzro Ledger MCP server (https://canton-mcp.tenzro.network/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 →