AI agents call vikunja_get_current_user to retrieve information from Vikunja without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves user profile and settings information without creating, modifying, deleting, or executing anything. It is a straightforward read operation on existing data accessible to the authenticated user. The blast radius of misuse is minimal—exposure of user profile data is low severity since it is already authenticated and accessible to that user's session.
From the tool's definition Tool name is 'vikunja_get_current_user' and description states 'Get the authenticated Vikunja user profile and settings' — a retrieval operation with no data modification or side effects.
Attacks that exploit this kind of access
Get the authenticated Vikunja user profile and settings for the configured credentials. 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 vikunja_get_current_user: 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.
vikunja_get_current_user 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 vikunja_get_current_user 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 vikunja_get_current_user. 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.
vikunja_get_current_user is provided by the Vikunja MCP server (shichao402/vikunja-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 →