搜索用户
AI agents call search_users to retrieve information from MCP Test Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool searches and retrieves user information from the system. The 'search' operation is inherently a read-only action that queries data without side effects. There is no indication of data creation, modification, deletion, or execution of code. Severity is low because searching user data has limited blast radius—the main risk is information disclosure, which is mitigated by normal access controls.
From the tool's definition Tool name 'search_users' and description '搜索用户' (search users in Chinese) indicate querying/retrieving user data with no modification capability.
Attacks that exploit this kind of access
搜索用户. It is categorised as a Read tool in the MCP Test Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Test Server MCP server in PolicyLayer and add a rule for search_users: 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 MCP Test Server. Nothing to install.
search_users 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_users 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_users. 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_users is provided by the MCP Test Server MCP server (small-tou/mcp-test). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
search_users is one line of MCP Test Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →