set_bridge_fee_rate
AI agents use set_bridge_fee_rate to commit financial operations through Tenzro Ledger MCP — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Setting a bridge fee rate directly affects financial transactions by changing the cost of cross-chain transfers. This is a financial configuration action with significant blast radius if misused (e.g., setting fees to 0 or 100%). The description is empty, lowering confidence slightly, but the name and server context strongly suggest a financial/write operation. Financial takes precedence over Write.
From the tool's definition Tool name 'set_bridge_fee_rate' on a server described as handling 'payments, staking, bridges' — implies modifying financial parameters for cross-chain bridge operations.
Attacks that exploit this kind of access
set_bridge_fee_rate. 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 set_bridge_fee_rate: 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.
set_bridge_fee_rate 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 set_bridge_fee_rate 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 set_bridge_fee_rate. 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.
set_bridge_fee_rate 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 →