顧客の詳細情報（住所、レンタル統計含む）を取得します。
AI agents call get_customer_details to retrieve information from Sakila MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns customer information without modifying, executing code, deleting data, or moving money. It has no side effects and is purely informational. Severity is low because exposing customer details like addresses and rental history, while sensitive, would not cause critical damage if misused by an AI agent — it is a read-only operation with limited blast radius in a database context.
From the tool's definition Tool name 'get_customer_details' and description indicating it 'retrieves customer detailed information (including address, rental statistics)' — the verb 'get' and 'retrieve' (from the Japanese description 取得します) indicate data retrieval only.
Attacks that exploit this kind of access
顧客の詳細情報（住所、レンタル統計含む）を取得します。. It is categorised as a Read tool in the Sakila MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sakila MCP Server MCP server in PolicyLayer and add a rule for get_customer_details: 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 Sakila MCP Server. Nothing to install.
get_customer_details 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_details 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_details. 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_details is provided by the Sakila MCP Server MCP server (mo3g4u/mcp-server-sample). 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 →