send_transaction
AI agents use send_transaction to commit financial operations through Tenzro Ledger MCP — usually the final step of a payment, billing, or trading workflow. A call moves real money.
On a financial ledger platform dealing with wallets, payments, staking, and bridges, 'send_transaction' almost certainly submits a blockchain transaction that moves assets. This is a Financial action with critical severity since misuse could result in irreversible loss of funds. Confidence is slightly reduced due to the empty description.
From the tool's definition Tool name 'send_transaction' on a server described as handling 'wallet, identity, payments, inference, staking, bridges, verification, agents' — the term 'send_transaction' strongly implies moving funds or committing financial operations on a…
Attacks that exploit this kind of access
send_transaction. 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 send_transaction: 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.
send_transaction 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 send_transaction 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 send_transaction. 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.
send_transaction 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 →