顧客の詳細情報を取得します
AI agents call get_customer to retrieve information from hokan MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves customer information from the hokan Insurance CRM API without any side effects. It is a straightforward read operation that queries existing data. While it accesses potentially sensitive customer data in an insurance context, the tool itself performs no destructive, financial, or executable actions—it only fetches information.
From the tool's definition Tool name 'get_customer' and description '顧客の詳細情報を取得します' (retrieve customer detailed information) indicate a data retrieval operation with no modification or deletion capabilities.
Attacks that exploit this kind of access
顧客の詳細情報を取得します. It is categorised as a Read tool in the hokan MCP Server MCP Server, which means it retrieves data without modifying state.
Register the hokan MCP Server MCP server in PolicyLayer and add a rule for get_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.
get_customer is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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 get_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.
get_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 →