rekey_account

Rekey an Algorand account to a new address

SERVERAlgorand MCP SOURCEgoplausible/algorand-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/goplausible-algorand-mcp/rekey-account.md

WHAT IT DOES

What rekey_account does on Algorand MCP

AI agents invoke rekey_account 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.

RISK

Why rekey_account is rated High

Rekeying an Algorand account transfers signing authority to a new address, meaning the original private key no longer controls the account. This is an irreversible authorization change on the blockchain — if misused, the original owner permanently loses control of their account and all its assets.

From the tool's definition Rekey an Algorand account to a new address

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs rekey_account 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 rekey_account, this is the rule to start with:

rekey_account Rate-limited

rekey_account 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "rekey_account": {
      "limits": [
        {
          "counter": "rekey_account_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Algorand MCP, apply this rule, and every rekey_account call is checked against it from then on.

FAQ

Questions about rekey_account

What does the rekey_account tool do? +

Rekey an Algorand account to a new address. 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.

How do I enforce a policy on rekey_account? +

Register the Algorand 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 Algorand MCP. Nothing to install.

What risk level is rekey_account? +

rekey_account is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit rekey_account? +

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.

How do I block rekey_account completely? +

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.

What MCP server provides rekey_account? +

rekey_account 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.

KEEP EXPLORING

More on Algorand, and thousands of servers like it.

This server

All 177 Algorand tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →