vikunja_projects_sharing
Project sharing operations (create_share, list_shares, get_share, delete_share, auth_share)
This record as markdown: /tools/democratize-technology-vikunja-mcp/vikunja-projects-sharing.md
What vikunja_projects_sharing does on Vikunja MCP Server
AI agents use vikunja_projects_sharing to create or update resources in Vikunja MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vikunja MCP Server environment.
Why vikunja_projects_sharing is rated Medium
The tool's primary capabilities (create_share, delete_share, auth_share) modify sharing permissions and access control settings. While delete_share removes a share link, this is reversible by creating a new share. The tool does not permanently destroy project data, execute arbitrary code, or process financial transactions. It fits the Write category as it creates, modifies, or removes sharing configurations.
From the tool's definition Tool performs project sharing operations including 'create_share', 'list_shares', 'get_share', 'delete_share', and 'auth_share'. Create and delete operations modify access control and sharing state; these are reversible changes to project permissions.
Attacks that exploit this kind of access
The rule that runs vikunja_projects_sharing 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_projects_sharing, this is the rule to start with:
vikunja_projects_sharing stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_projects_sharing call is checked against it from then on.
Questions about vikunja_projects_sharing
Project sharing operations (create_share, list_shares, get_share, delete_share, auth_share). It is categorised as a Write tool in the Vikunja MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Vikunja MCP Server MCP server in PolicyLayer and add a rule for vikunja_projects_sharing: 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_projects_sharing is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the vikunja_projects_sharing 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_projects_sharing. 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_projects_sharing 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.
This server
Across the catalogue