filter_list
List filters applied to a specific layer.
This record as markdown: /tools/mcp-anything/filter-list.md
What filter_list does on Mcp Anything
AI agents call filter_list to retrieve information from Mcp Anything without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why filter_list is rated Low
This tool queries and returns information about filters on a layer without modifying, deleting, or executing any operations. It is a straightforward read operation that retrieves existing state. The low severity reflects minimal blast radius if an AI agent misuses it—it can only retrieve data about layer filters.
From the tool's definition Tool name 'filter_list' and description 'List filters applied to a specific layer' indicates a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs filter_list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Anything, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For filter_list, this is the rule to start with:
filter_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 Mcp Anything, apply this rule, and every filter_list call is checked against it from then on.
Questions about filter_list
List filters applied to a specific layer. It is categorised as a Read tool in the Mcp Anything MCP Server, which means it retrieves data without modifying state.
Register the Mcp Anything MCP server in PolicyLayer and add a rule for filter_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 Mcp Anything. Nothing to install.
filter_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 filter_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 filter_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.
filter_list is provided by the Mcp Anything MCP server (Zaymadkid/mcp-anything). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Anything, and thousands of servers like it.
This server
Across the catalogue