AI agents call search_users to retrieve information from Mcp Gitee without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
q | string | Yes | Search keywords |
page | number | — | Page number |
per_page | number | — | Number of results per page |
Parameters from the server's own tool schema.
This tool performs a search query to retrieve user data from Gitee, which is a read-only operation with no side effects. It does not create, modify, delete, or execute any actions. The blast radius is minimal as it only exposes publicly searchable user information.
From the tool's definition Tool name 'search_users' and description 'Search users on Gitee' indicate a query operation that retrieves user information without modifying data.
Attacks that exploit this kind of access
Search users on Gitee. It is categorised as a Read tool in the Mcp Gitee MCP Server, which means it retrieves data without modifying state.
search_users accepts 3 parameters: q, page, per_page. Required: q. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Gitee 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 Gitee. 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 Gitee MCP server (@gitee/mcp-gitee). 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 →