Verify the 6-digit code sent to your email after register_owner. This completes registration and activates your workspace. Ask the user to check their email and paste the code.
AI agents use verify_code to create or update resources in APIClaw — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your APIClaw environment.
This tool completes an account registration flow by verifying an email code, which activates a workspace. It creates/modifies persistent account state (activating a workspace), making it a Write operation. It is not destructive, financial, or arbitrary code execution. Severity is medium because misuse could activate workspaces under false pretenses, but blast radius is limited to account provisioning.
From the tool's definition Verify the 6-digit code sent to your email after register_owner. This completes registration and activates your workspace.
Documented attack patterns abuse exactly the kind of access verify_code gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and APIClaw, and nothing reaches the server without passing your rules. This is the rule we recommend for verify_code:
{
"version": "1",
"default": "deny",
"tools": {
"verify_code": {
"limits": [
{
"counter": "verify_code_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}verify_code 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.
Verify the 6-digit code sent to your email after register_owner. This completes registration and activates your workspace. Ask the user to check their email and paste the code. It is categorised as a Write tool in the APIClaw MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the APIClaw MCP server in PolicyLayer and add a rule for verify_code: 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 APIClaw. Nothing to install.
verify_code 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 verify_code 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 verify_code. 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.
verify_code is provided by the APIClaw MCP server (nordsym/apiclaw). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from APIClaw, 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.
24 APIClaw tools catalogued and risk-classified — across an index of 43,000+ MCP servers.