AI agents use api_ultrade_wallet_add_key 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.
This tool creates or adds data (a trading key) to a wallet, making it a Write operation. However, the severity is elevated to 'high' rather than standard 'medium' because adding trading keys to a wallet grants new authorization/authentication capabilities that could enable unauthorized trading if misused by an AI agent.
From the tool's definition 'Add a trading key' modifies wallet configuration by adding a new cryptographic key, which is a persistent data change to authentication/authorization state.
Documented attack patterns abuse exactly the kind of access api_ultrade_wallet_add_key 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 api_ultrade_wallet_add_key:
{
"version": "1",
"default": "deny",
"tools": {
"api_ultrade_wallet_add_key": {
"limits": [
{
"counter": "api_ultrade_wallet_add_key_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} api_ultrade_wallet_add_key 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.
Add a trading key. 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 api_ultrade_wallet_add_key: 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.
api_ultrade_wallet_add_key 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 api_ultrade_wallet_add_key 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 api_ultrade_wallet_add_key. 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.
api_ultrade_wallet_add_key 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.