AI agents use create_customer to create or update resources in Paymongo — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Paymongo environment.
This tool creates and persists customer records containing PII (personally identifiable information), which is a reversible write operation. While it doesn't move money directly (which would make it Financial), it stores sensitive customer data that could be misused if an agent creates unauthorized customer records with stolen PII or spam data.
From the tool's definition Tool description states 'Create a customer record' and 'stores PII for reuse across payments'. The verb 'Create' and action of storing personally identifiable information (PII) indicates data creation and persistence.
Attacks that exploit this kind of access
Create a customer record (stores PII for reuse across payments). It is categorised as a Write tool in the Paymongo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Paymongo MCP server in PolicyLayer and add a rule for create_customer: 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 Paymongo. Nothing to install.
create_customer 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_customer 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_customer. 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_customer is provided by the Paymongo MCP server (theyahia/paymongo-mcp). 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 →