List all saved MantisBT issue filters accessible to the current user. Filter IDs can be used with list_issues.
AI agents call list_filters to retrieve information from MantisBT MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves existing filter configurations without modifying, deleting, or executing any operations. It is a passive information retrieval function, fitting the Read category. Severity is low because exposure of filter metadata presents minimal risk—filters are typically user-level artifacts and do not directly access sensitive issue data themselves.
From the tool's definition Tool name 'list_filters' and description 'List all saved MantisBT issue filters' indicate a retrieval operation with no side effects. Returns metadata about filters for use with other tools.
Attacks that exploit this kind of access
List all saved MantisBT issue filters accessible to the current user. Filter IDs can be used with list_issues. It is categorised as a Read tool in the MantisBT MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MantisBT MCP Server MCP server in PolicyLayer and add a rule for list_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 MantisBT MCP Server. Nothing to install.
list_filters 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 list_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.
Set action: deny in the PolicyLayer policy for list_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.
list_filters is provided by the MantisBT MCP Server MCP server (@dpesch/mantisbt-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
list_filters is one line of MantisBT MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →