This record as markdown: /tools/0xk3vin-vikunja-mcp/users-search.md
What users_search does on Vikunja
AI agents call users_search to retrieve information from Vikunja without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why users_search is rated Low
This tool retrieves or queries user data without creating, modifying, deleting, or executing any operations. It performs a search operation which is a read-only action. Severity is low because search results of user metadata poses minimal risk even if misused—it returns informational data without enabling account compromise, financial transactions, or data destruction.
From the tool's definition Tool description explicitly states 'Search for users' which is a retrieval operation with no modification or side effects. The function name 'users_search' and description indicate querying user information by username, name, or email.
Attacks that exploit this kind of access
The rule that runs users_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Vikunja, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For users_search, this is the rule to start with:
users_search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Vikunja, apply this rule, and every users_search call is checked against it from then on.
Questions about users_search
Search for users by username, name, or email. It is categorised as a Read tool in the Vikunja MCP Server, which means it retrieves data without modifying state.
Register the Vikunja MCP server in PolicyLayer and add a rule for 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 Vikunja. Nothing to install.
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 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 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.
users_search is provided by the Vikunja MCP server (0xk3vin/vikunja-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vikunja, and thousands of servers like it.
This server
Across the catalogue