Register a new customer in the system. This tool must be used everytime a customer send any information about himself. Required fields: name, email, phone, zipcode and identification. Optional fields include address details, UTM parameters, and tags. Returns a success and proceed to show the offe...
AI agents use createCustomer to create or update resources in Customer Registration MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Customer Registration MCP Server environment.
createCustomer creates and stores new customer records with personally identifiable information (name, email, phone, address, identification). This is a Write operation because it creates data that persists in the system, is reversible (records can typically be updated or deactivated), and has no financial implications by itself (though it enables downstream financial operations via sibling tools createPayment and…
From the tool's definition Tool description states it 'Register a new customer in the system' and 'creates' customer records; accepts 'Required fields: name, email, phone, zipcode and identification' with 'Optional fields include address details, UTM parameters, and tags.' The server…
Attacks that exploit this kind of access
Register a new customer in the system. This tool must be used everytime a customer send any information about himself. Required fields: name, email, phone, zipcode and identification. Optional fields include address details, UTM parameters, and tags. Returns a success and proceed to show the offers using the mcp tool. It is categorised as a Write tool in the Customer Registration MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Customer Registration MCP Server MCP server in PolicyLayer and add a rule for createCustomer: 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 Customer Registration MCP Server. Nothing to install.
createCustomer 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 createCustomer 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 createCustomer. 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.
createCustomer is provided by the Customer Registration MCP Server MCP server (rodrigoai/mcpnova). 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 →