Get a saved filter by ID.
AI agents call get_filter to retrieve information from Vikunja MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves an existing filter configuration by its identifier. It performs a simple lookup/fetch operation with no ability to modify, delete, or execute actions. The blast radius of misuse is minimal—an attacker gains only visibility into a saved filter's definition, which is low-risk information disclosure. Categorized as Read with low severity.
From the tool's definition Tool name 'get_filter' and description 'Get a saved filter by ID' indicate a retrieval operation with no side effects. The verb 'Get' and the absence of any modification language confirm this is a read-only query.
Attacks that exploit this kind of access
Get a saved filter by ID. It is categorised as a Read tool in the Vikunja MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Vikunja MCP Server MCP server in PolicyLayer and add a rule for get_filter: 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.
get_filter 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 get_filter 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 get_filter. 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.
get_filter is provided by the Vikunja MCP Server MCP server (lindenlion/vikunja-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →