create_api_key
Create a new personal API key for the user. Returns the full key (shown only once). Useful when the user needs a key for a new tool, service, or environment.
This record as markdown: /tools/agentpay/create-api-key.md
What create_api_key does on Agentpay
AI agents use create_api_key to create or update resources in Agentpay, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Agentpay environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | Label for the key (e.g. 'cursor', 'ci-pipeline') |
Parameters from the server's own tool schema.
Why create_api_key is rated Medium
Creating API keys is a write operation that modifies the user's security configuration by adding a new credential. While not directly financial, it is a high-severity write action because a compromised API key could grant unauthorized access to AgentPay's payment and account services (evidenced by sibling tools like create_card, fill_card, detect_checkout, and check_balance).
From the tool's definition Tool creates a new personal API key; description states 'Create a new personal API key for the user' and notes the key is 'shown only once', indicating generation of a credential that will be persisted.
Attacks that exploit this kind of access
The rule that runs create_api_key safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Agentpay, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_api_key, this is the rule to start with:
create_api_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Agentpay, apply this rule, and every create_api_key call is checked against it from then on.
Questions about create_api_key
Create a new personal API key for the user. Returns the full key (shown only once). Useful when the user needs a key for a new tool, service, or environment. It is categorised as a Write tool in the Agentpay MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_api_key accepts 1 parameter: name. The full parameter table on this page comes from the server's own tool schema.
Register the Agentpay MCP server in PolicyLayer and add a rule for create_api_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 Agentpay. Nothing to install.
create_api_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 create_api_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 create_api_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.
create_api_key is provided by the Agentpay MCP server (agentpay-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Agentpay, and thousands of servers like it.
This server
Across the catalogue