New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

vikunja_projects_sharing

Project sharing operations (create_share, list_shares, get_share, delete_share, auth_share)

SERVERVikunja MCP Server SOURCEdemocratize-technology/vikunja-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about vikunja_projects_sharing

What does the vikunja_projects_sharing tool do? +

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.

How do I enforce a policy on vikunja_projects_sharing? +

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.

What risk level is vikunja_projects_sharing? +

vikunja_projects_sharing is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit vikunja_projects_sharing? +

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.

How do I block vikunja_projects_sharing completely? +

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.

What MCP server provides vikunja_projects_sharing? +

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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Vikunja MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.