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.
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
Documented attack patterns abuse exactly the kind of access assign_group_id gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Algorand MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for assign_group_id:
{
"version": "1",
"default": "deny",
"tools": {
"assign_group_id": {
"limits": [
{
"counter": "assign_group_id_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
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.
Start from Algorand MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
172 Algorand MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.