AI agents use make_asset_config_txn to create or update resources in Algorand MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Algorand MCP environment.
Asset configuration transactions modify the parameters of an existing Algorand Standard Asset (ASA), such as changing the manager, reserve, freeze, or clawback addresses. This is a Write operation as it modifies on-chain asset configuration. However, misconfiguration (e.g., setting clawback or freeze addresses to malicious parties) can have significant security implications, justifying high severity.
From the tool's definition Create an asset configuration transaction
Documented attack patterns abuse exactly the kind of access make_asset_config_txn 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 make_asset_config_txn:
{
"version": "1",
"default": "deny",
"tools": {
"make_asset_config_txn": {
"limits": [
{
"counter": "make_asset_config_txn_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}make_asset_config_txn stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create an asset configuration transaction. It is categorised as a Write tool in the Algorand MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Algorand MCP server in PolicyLayer and add a rule for make_asset_config_txn: 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.
make_asset_config_txn is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the make_asset_config_txn 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 make_asset_config_txn. 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.
make_asset_config_txn 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.