新規顧客(個人)を作成します
AI agents use create_customer to create or update resources in hokan MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your hokan MCP Server environment.
The tool creates new customer entries in a CRM database. This is a Write operation because it creates data that can be modified or deleted later (as evidenced by the sibling delete_customer tool). Severity is medium because: (1) it modifies sensitive customer data in a financial services context, (2) but the operation is reversible via delete_customer, and (3) it doesn't directly move money or delete data.
From the tool's definition Tool name 'create_customer' and description '新規顧客(個人)を作成します' (creates a new individual customer) indicate data creation. This is a reversible write operation on customer records in an insurance CRM system.
Attacks that exploit this kind of access
新規顧客(個人)を作成します. It is categorised as a Write tool in the hokan MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the hokan MCP Server 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 hokan MCP Server. 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 hokan MCP Server MCP server (shinonft/hokan-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 →