Remove all domain filters (both allowed and blocked) and recency filter. Use when switching search contexts or starting fresh.
AI agents use clear_filters to create or update resources in Perplexity MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Perplexity MCP Server environment.
This tool modifies search configuration state by clearing/resetting filters. It is reversible (filters can be re-added), so it falls under Write rather than Destructive. The blast radius is low as it only affects search filter settings, not actual data or external systems.
From the tool's definition Remove all domain filters (both allowed and blocked) and recency filter
Attacks that exploit this kind of access
Remove all domain filters (both allowed and blocked) and recency filter. Use when switching search contexts or starting fresh. It is categorised as a Write tool in the Perplexity MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Perplexity MCP Server MCP server in PolicyLayer and add a rule for clear_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.
clear_filters is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the clear_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 clear_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.
clear_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 →