agentpay_signup
Create an AgentPay account for the user. Call this with their email to enable payment tools. Only needed once.
This record as markdown: /tools/agentpay/agentpay-signup.md
What agentpay_signup does on Agentpay
AI agents use agentpay_signup 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 | — | User's name |
email | string | Yes | User's email address |
Parameters from the server's own tool schema.
Why agentpay_signup is rated Medium
This tool creates a new user account, which is a Write operation (reversible creation of data). Severity is medium because account creation in a financial platform could enable subsequent financial transactions if the agent misuses companion tools, but the signup itself does not directly move money or delete data.
From the tool's definition Tool description states 'Create an AgentPay account' which is a reversible data creation operation. The context of a payment platform (AgentPay) and the sibling tools (check_account, create_card, create_api_key) confirm this is account creation/initialization.
Attacks that exploit this kind of access
The rule that runs agentpay_signup 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 agentpay_signup, this is the rule to start with:
agentpay_signup 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 agentpay_signup call is checked against it from then on.
Questions about agentpay_signup
Create an AgentPay account for the user. Call this with their email to enable payment tools. Only needed once. 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.
agentpay_signup accepts 2 parameters: name, email. Required: email. 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 agentpay_signup: 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.
agentpay_signup 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 agentpay_signup 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 agentpay_signup. 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.
agentpay_signup 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