Search for users by email address
AI agents call docs_search_users to retrieve information from Docs MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only search operation to retrieve user information based on email criteria. It has no side effects, does not modify data, and does not execute external operations. The blast radius of misuse is minimal—an attacker could enumerate users in the system but cannot access sensitive document content or perform destructive actions with this tool alone. Classified as Read with low severity.
From the tool's definition The tool 'docs_search_users' with description 'Search for users by email address' retrieves information without modifying, creating, or deleting any data. This is a straightforward query operation.
Attacks that exploit this kind of access
Search for users by email address. It is categorised as a Read tool in the Docs MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Docs MCP Server MCP server in PolicyLayer and add a rule for docs_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 Docs MCP Server. Nothing to install.
docs_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 docs_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 docs_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.
docs_search_users is provided by the Docs MCP Server MCP server (nic01asfr/docs-mcp-server). 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 →