Register for an API key. Provide your email to get a key immediately.
AI agents use register to create or update resources in QR for Agent — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your QR for Agent environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
email | string | Yes | Your email address. |
label | string | — | An optional label to identify this API key. |
Parameters from the server's own tool schema.
The tool creates and stores user registration data (API key and email association) in the system. This is a reversible write operation—the registration and key can be modified or revoked. It does not execute arbitrary code, delete data irreversibly, or move money. While it does modify state, it is not destructive.
From the tool's definition Tool description states 'Register for an API key. Provide your email to get a key immediately.' This creates a new API key record and stores user email, which is data creation with side effects.
Attacks that exploit this kind of access
Register for an API key. Provide your email to get a key immediately. It is categorised as a Write tool in the QR for Agent MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
register accepts 2 parameters: email, label. Required: email. The full parameter table on this page comes from the server's own tool schema.
Register the QR for Agent MCP server in PolicyLayer and add a rule for register: 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 QR for Agent. Nothing to install.
register 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 register 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 register. 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.
register is provided by the QR for Agent MCP server (qr-for-agent). 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 →