assign_group_id
Assign a group ID to a list of transactions
This record as markdown: /tools/goplausible-algorand-mcp/assign-group-id.md
What assign_group_id does on Algorand MCP
AI agents invoke assign_group_id 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 assign_group_id is rated High
This tool modifies transaction objects by assigning group IDs, which is a preparatory step for atomic transaction groups on the Algorand blockchain. It doesn't move money directly but triggers a blockchain operation setup that enables atomic execution. It goes beyond a simple read and modifies transaction state, placing it in the Execute category as it prepares transactions for grouped execution.
From the tool's definition Assign a group ID to a list of transactions
Attacks that exploit this kind of access
The rule that runs assign_group_id 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 assign_group_id, this is the rule to start with:
assign_group_id 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 assign_group_id call is checked against it from then on.
Questions about assign_group_id
Assign a group ID to a list of transactions. 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 assign_group_id: 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.
assign_group_id 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 assign_group_id 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 assign_group_id. 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.
assign_group_id 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