wallet_sign_transaction_group
Sign a group of transactions with the active wallet account. Assigns group ID automatically.
This record as markdown: /tools/goplausible-algorand-mcp/wallet-sign-transaction-group.md
What wallet_sign_transaction_group does on Algorand MCP
AI agents invoke wallet_sign_transaction_group 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 wallet_sign_transaction_group is rated High
Signing a group of transactions is a prerequisite to broadcasting them to the blockchain. While signing alone doesn't submit, in most MCP/agent contexts this operation is part of an automated flow that leads directly to execution of on-chain transactions. The tool operates on potentially multiple transactions at once (group), amplifying the blast radius.
From the tool's definition Sign a group of transactions with the active wallet account. Assigns group ID automatically.
Attacks that exploit this kind of access
The rule that runs wallet_sign_transaction_group 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 wallet_sign_transaction_group, this is the rule to start with:
wallet_sign_transaction_group 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 wallet_sign_transaction_group call is checked against it from then on.
Questions about wallet_sign_transaction_group
Sign a group of transactions with the active wallet account. Assigns group ID automatically. 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 wallet_sign_transaction_group: 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.
wallet_sign_transaction_group 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 wallet_sign_transaction_group 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 wallet_sign_transaction_group. 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.
wallet_sign_transaction_group 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