projects_list

List all projects the user has access to

SERVERVikunja SOURCE0xk3vin/vikunja-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/0xk3vin-vikunja-mcp/projects-list.md

WHAT IT DOES

What projects_list does on Vikunja

AI agents call projects_list 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.

RISK

Why projects_list is rated Low

This tool queries and returns data about projects without modifying, deleting, or executing any operations. It is a straightforward read-only action that retrieves information the authenticated user is already authorized to see.

From the tool's definition Tool name is 'projects_list' and description states 'List all projects the user has access to' - a retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs projects_list 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 projects_list, this is the rule to start with:

projects_list Allowed

projects_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "projects_list": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Vikunja, apply this rule, and every projects_list call is checked against it from then on.

FAQ

Questions about projects_list

What does the projects_list tool do? +

List all projects the user has access to. It is categorised as a Read tool in the Vikunja MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on projects_list? +

Register the Vikunja MCP server in PolicyLayer and add a rule for projects_list: 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.

What risk level is projects_list? +

projects_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit projects_list? +

Yes. Add a rate_limit block to the projects_list 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 projects_list completely? +

Set action: deny in the PolicyLayer policy for projects_list. 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 projects_list? +

projects_list 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.

KEEP EXPLORING

More on Vikunja, and thousands of servers like it.

This server

All 31 Vikunja tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →