List available filter values for Solodit search (firms, tags, categories, languages). Use this to discover valid values for search_findings filters.
AI agents call get_filter_options to retrieve information from Claudit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool simply enumerates valid filter options (firms, tags, categories, languages) from the Solodit database. It retrieves metadata about available filters to support search operations, with no side effects, data modification, code execution, or financial implications. It is a pure read operation.
From the tool's definition Tool lists and retrieves filter values for search parameters; described as enabling discovery of valid filter options without modifying any data. The verb 'list' and function of discovering available options are characteristic of read-only operations.
Documented attack patterns abuse exactly the kind of access get_filter_options gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Claudit, and nothing reaches the server without passing your rules. This is the rule we recommend for get_filter_options:
{
"version": "1",
"default": "deny",
"tools": {
"get_filter_options": {}
}
}get_filter_options is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List available filter values for Solodit search (firms, tags, categories, languages). Use this to discover valid values for search_findings filters. It is categorised as a Read tool in the Claudit MCP Server, which means it retrieves data without modifying state.
Register the Claudit MCP server in PolicyLayer and add a rule for get_filter_options: 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 Claudit. Nothing to install.
get_filter_options 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_options 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_options. 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_options is provided by the Claudit MCP server (marchev/claudit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Claudit, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 Claudit tools catalogued and risk-classified — across an index of 43,000+ MCP servers.