Display current filter configuration including allowed domains, blocked domains, and active recency setting. Useful for debugging search behavior.
AI agents call list_filters to retrieve information from Perplexity 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 and displays the current state of search filters (allowed domains, blocked domains, recency settings). It has no side effects, does not execute code or commands, does not create or modify data, and does not involve financial transactions. It is purely informational and read-only.
From the tool's definition Tool name 'list_filters' and description 'Display current filter configuration' indicates retrieval of configuration state with no modification or execution of external actions.
Attacks that exploit this kind of access
Display current filter configuration including allowed domains, blocked domains, and active recency setting. Useful for debugging search behavior. It is categorised as a Read tool in the Perplexity MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Perplexity 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 Perplexity 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 Perplexity MCP Server MCP server (rossh121/perplexity-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 →