Search users by name or email.
AI agents call wiki_users_search to retrieve information from Mcp Wikijs Mv without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves user information based on search criteria (name or email) without creating, modifying, deleting, or executing any operations. It is a simple query operation with no side effects, fitting the Read category. Severity is low because user directory information is typically non-sensitive in a wiki context and exposure carries minimal blast radius.
From the tool's definition Tool name is 'wiki_users_search' and description states it 'Search users by name or email.' The verb 'search' and the read-only nature of querying user data without modification indicate a retrieval operation.
Attacks that exploit this kind of access
Search users by name or email. It is categorised as a Read tool in the Mcp Wikijs Mv MCP Server, which means it retrieves data without modifying state.
Register the Mcp Wikijs Mv MCP server in PolicyLayer and add a rule for wiki_users_search: 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 Wikijs Mv. Nothing to install.
wiki_users_search 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 wiki_users_search 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 wiki_users_search. 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.
wiki_users_search is provided by the Mcp Wikijs Mv MCP server (janschachtschabel/mcp-for-wiki-js). 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 →