vikunja_filters

Manage and build advanced filters for tasks and projects with validation

SERVERVikunja MCP Server SOURCEdemocratize-technology/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/democratize-technology-vikunja-mcp/vikunja-filters.md

WHAT IT DOES

What vikunja_filters does on Vikunja MCP Server

AI agents call vikunja_filters to retrieve information from Vikunja MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why vikunja_filters is rated Low

The tool is described as managing and building filters, which are query/search constructs used to retrieve filtered views of tasks and projects. Filters themselves don't modify underlying data — they define how data is queried. The 'manage' aspect could imply write operations (saving/deleting filters), but the primary function is constructing read queries.

From the tool's definition 'Manage and build advanced filters for tasks and projects with validation'

Attacks that exploit this kind of access

RECOMMENDED RULE

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

vikunja_filters Allowed

vikunja_filters 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": {
    "vikunja_filters": {}
  }
}

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

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

FAQ

Questions about vikunja_filters

What does the vikunja_filters tool do? +

Manage and build advanced filters for tasks and projects with validation. It is categorised as a Read tool in the Vikunja MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on vikunja_filters? +

Register the Vikunja MCP Server MCP server in PolicyLayer and add a rule for vikunja_filters: 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_filters? +

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

Can I rate-limit vikunja_filters? +

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

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

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

KEEP EXPLORING

More on Vikunja MCP Server, and thousands of servers like it.

This server

All 23 Vikunja MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

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