vikunja_request_user_export
Request a complete export of user data for privacy and backup purposes
This record as markdown: /tools/democratize-technology-vikunja-mcp/vikunja-request-user-export.md
What vikunja_request_user_export does on Vikunja MCP Server
AI agents invoke vikunja_request_user_export to trigger actions in Vikunja MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why vikunja_request_user_export is rated High
This tool triggers an external operation (requesting a data export) rather than directly reading data. It initiates a server-side process that compiles and packages user data, which is an action with side effects (creating an export job/file on the server). It doesn't simply retrieve existing data — it causes the system to generate a new artifact.
From the tool's definition Request a complete export of user data for privacy and backup purposes
Attacks that exploit this kind of access
The rule that runs vikunja_request_user_export safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Vikunja MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For vikunja_request_user_export, this is the rule to start with:
vikunja_request_user_export stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Vikunja MCP Server, apply this rule, and every vikunja_request_user_export call is checked against it from then on.
Questions about vikunja_request_user_export
Request a complete export of user data for privacy and backup purposes. It is categorised as a Execute tool in the Vikunja MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Vikunja MCP Server MCP server in PolicyLayer and add a rule for vikunja_request_user_export: 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 MCP Server. Nothing to install.
vikunja_request_user_export is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the vikunja_request_user_export 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_request_user_export. 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_request_user_export is provided by the Vikunja MCP Server MCP server (democratize-technology/vikunja-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vikunja MCP Server, and thousands of servers like it.
Across the catalogue