Send Algo payment transaction (WARNING: Requires mnemonic phrase)
AI agents use send_payment to commit financial operations through Algorand MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool transfers Algo tokens between accounts on a live blockchain, constituting a financial transaction. It requires a mnemonic (private key), meaning it can irreversibly move funds. Misuse could result in loss of funds with no recourse, making it critical severity.
From the tool's definition 'Send Algo payment transaction' — moves cryptocurrency (Algo) on the Algorand blockchain; '(WARNING: Requires mnemonic phrase)' confirms it signs and broadcasts real financial transactions
Attacks that exploit this kind of access
Send Algo payment transaction (WARNING: Requires mnemonic phrase). It is categorised as a Financial tool in the Algorand MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Algorand MCP Server MCP server in PolicyLayer and add a rule for send_payment: 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 Algorand MCP Server. Nothing to install.
send_payment 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_payment 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_payment. 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_payment is provided by the Algorand MCP Server MCP server (jake-loranger/algorand-mcp-server). 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 →