按名称搜索瑞幸门店。首次使用需提供经纬度，之后用记忆的常用门店坐标。
AI agents call findShop to retrieve information from Luckin Mcp Proxy without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward search/query operation that retrieves shop location data. It has no side effects—it only queries and returns information about coffee shops. The tool fits the Read category: it retrieves data without modifying, deleting, or executing external operations. Low severity due to limited blast radius; misuse would only return shop location information.
From the tool's definition Tool description indicates 'search' functionality (按名称搜索 = search by name) for Luckin Coffee shops. Returns shop information based on name and location coordinates. No data modification, deletion, or external actions triggered.
Attacks that exploit this kind of access
按名称搜索瑞幸门店。首次使用需提供经纬度，之后用记忆的常用门店坐标。. It is categorised as a Read tool in the Luckin Mcp Proxy MCP Server, which means it retrieves data without modifying state.
Register the Luckin Mcp Proxy MCP server in PolicyLayer and add a rule for findShop: 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 Luckin Mcp Proxy. Nothing to install.
findShop 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 findShop 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 findShop. 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.
findShop is provided by the Luckin Mcp Proxy MCP server (wyhacc/luckin-mcp-proxy). 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 →