顧客を検索します。名前、メール、店舗で絞り込みできます。
AI agents call search_customers 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 is a query operation that retrieves customer information based on filter criteria (name, email, store). It has no side effects—no data is created, modified, or deleted. It aligns with the 'Read' category as a retrieval/search function. The low severity reflects minimal blast radius; misuse would only expose existing customer data, not enable financial transactions, destructive operations, or code execution.
From the tool's definition Tool name 'search_customers' and description indicating it searches/filters customers by name, email, and store without modification capabilities. Description translates to 'Search customers. Can filter by name, email, store.'
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 search_customers: 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.
search_customers 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 search_customers 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 search_customers. 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.
search_customers 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 →