AI agents use create_wallet to create or update resources in Cardzero — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cardzero environment.
This tool creates new data (a wallet) that persists and affects subsequent operations on Base chain. It is Write rather than Execute because it doesn't run arbitrary code or external operations—it simply instantiates a wallet resource.
From the tool's definition Create a new CardZero wallet. Returns a wallet address and one-time claim key — this creates a persistent cryptographic wallet object with associated credentials.
Attacks that exploit this kind of access
Create a new CardZero wallet. Returns a wallet address and one-time claim key for the human owner. No authentication required. It is categorised as a Write tool in the Cardzero MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Cardzero MCP server in PolicyLayer and add a rule for create_wallet: 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 Cardzero. Nothing to install.
create_wallet 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 create_wallet 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 create_wallet. 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.
create_wallet is provided by the Cardzero MCP server (mrocker/cardzero-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →