根据省份和城市名称获取景点数据（从本地JSON文件读取）
AI agents call get_spots_by_city to retrieve information from Chinese Tourism Spots 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 scenic spot information based on geographic parameters. It reads from a local data source without modifying, deleting, or executing any external operations. This is a straightforward read operation with minimal risk.
From the tool's definition Tool name 'get_spots_by_city' and description '根据省份和城市名称获取景点数据（从本地JSON文件读取）' [retrieve scenic spot data by province and city name from local JSON file] clearly indicate data retrieval with no side effects.
Attacks that exploit this kind of access
根据省份和城市名称获取景点数据（从本地JSON文件读取）. It is categorised as a Read tool in the Chinese Tourism Spots MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Chinese Tourism Spots MCP Server MCP server in PolicyLayer and add a rule for get_spots_by_city: 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 Chinese Tourism Spots MCP Server. Nothing to install.
get_spots_by_city 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_spots_by_city 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_spots_by_city. 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_spots_by_city is provided by the Chinese Tourism Spots MCP Server MCP server (sekusrevo/mcpproject). 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 →