This record as markdown: /tools/0xk3vin-vikunja-mcp/teams-list.md
What teams_list does on Vikunja
AI agents call teams_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.
Why teams_list is rated Low
This tool retrieves information about teams the user is a member of without creating, modifying, deleting, or executing any actions. It has no side effects and is purely informational. Low severity as exposing team membership data has limited blast radius if misused by an AI agent.
From the tool's definition Tool name is 'teams_list' and description states 'List all teams the user belongs to'. The verb 'list' and action of retrieving/enumerating teams without modification are characteristic of Read operations.
Attacks that exploit this kind of access
The rule that runs teams_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 teams_list, this is the rule to start with:
teams_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Vikunja, apply this rule, and every teams_list call is checked against it from then on.
Questions about teams_list
List all teams the user belongs to. 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 teams_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.
teams_list 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 teams_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.
Set action: deny in the PolicyLayer policy for teams_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.
teams_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.
More on Vikunja, and thousands of servers like it.
This server
Across the catalogue