Search for users by name or email. Returns matching user profiles for collaboration context.
AI agents call wikijs_search_users to retrieve information from Requarks Wiki 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 user information without modifying, deleting, or executing any operations. It is a straightforward read operation that retrieves user profile data for informational purposes. The low severity reflects minimal blast radius—exposing user contact information is a privacy concern but not operationally destructive.
From the tool's definition Tool name contains 'search' and description states 'Search for users by name or email. Returns matching user profiles' — retrieval operation with no side effects.
Attacks that exploit this kind of access
Search for users by name or email. Returns matching user profiles for collaboration context. It is categorised as a Read tool in the Requarks Wiki MCP Server, which means it retrieves data without modifying state.
Register the Requarks Wiki MCP server in PolicyLayer and add a rule for wikijs_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 Requarks Wiki. Nothing to install.
wikijs_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 wikijs_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 wikijs_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.
wikijs_search_users is provided by the Requarks Wiki MCP server (uyu423/requarks-wiki-mcp). 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 →