Rekey an Algorand account to a new address
AI agents use rekey_account to create or update resources in Sperax Ecosystem Crypto & DeFI MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sperax Ecosystem Crypto & DeFI MCP Server environment.
Rekeying an Algorand account changes the authoritative signing key for that account to a new address, which is a highly sensitive write operation. If misused, it can effectively transfer control of the account to an attacker, making all future transactions require the new key. While technically reversible (you can rekey again), losing access to the new key would be catastrophic.
From the tool's definition Rekey an Algorand account to a new address
Documented attack patterns abuse exactly the kind of access rekey_account gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sperax Ecosystem Crypto & DeFI MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for rekey_account:
{
"version": "1",
"default": "deny",
"tools": {
"rekey_account": {
"limits": [
{
"counter": "rekey_account_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} rekey_account 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.
Rekey an Algorand account to a new address. It is categorised as a Write tool in the Sperax Ecosystem Crypto & DeFI MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sperax Ecosystem Crypto & DeFI MCP Server MCP server in PolicyLayer and add a rule for rekey_account: 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 Sperax Ecosystem Crypto & DeFI MCP Server. Nothing to install.
rekey_account 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 rekey_account 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 rekey_account. 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.
rekey_account is provided by the Sperax Ecosystem Crypto & DeFI MCP Server MCP server (sperax/sperax-crypto-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Sperax Ecosystem Crypto & DeFI MCP Server, 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.
1318 Sperax Ecosystem Crypto & DeFI MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.