send_raw_transaction
Submit signed transactions to the Algorand network
This record as markdown: /tools/goplausible-algorand-mcp/send-raw-transaction.md
What send_raw_transaction does on Algorand MCP
AI agents invoke send_raw_transaction to trigger actions in Algorand 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.
Why send_raw_transaction is rated High
This tool submits pre-signed transactions to the blockchain network. While the transactions are already signed (so auth is handled), executing them triggers irreversible on-chain state changes (transfers, contract calls, etc.).
From the tool's definition Submit signed transactions to the Algorand network
Attacks that exploit this kind of access
The rule that runs send_raw_transaction safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Algorand MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For send_raw_transaction, this is the rule to start with:
send_raw_transaction stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Algorand MCP, apply this rule, and every send_raw_transaction call is checked against it from then on.
Questions about send_raw_transaction
Submit signed transactions to the Algorand network. It is categorised as a Execute tool in the Algorand MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Algorand MCP server in PolicyLayer and add a rule for send_raw_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 Algorand MCP. Nothing to install.
send_raw_transaction 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 send_raw_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_raw_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_raw_transaction is provided by the Algorand MCP server (goplausible/algorand-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Algorand, and thousands of servers like it.
Across the catalogue