This record as markdown: /tools/999md-mcp/get-filters.md
What get_filters does on 999md
AI agents call get_filters to retrieve information from 999md without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_filters is rated Low
The 'get_' prefix uniformly appears on sibling tools that retrieve CRM data (deals, persons, organizations, activities). 'get_filters' almost certainly retrieves filter definitions or saved filters from Pipedrive, a read-only operation. Confidence is slightly reduced due to empty description, but the naming pattern and server context provide strong evidence of a Read classification.
From the tool's definition Tool name 'get_filters' indicates a retrieval operation with the 'get_' prefix, consistent with sibling read-only tools (get_activities, get_deal, get_person, etc.).
Attacks that exploit this kind of access
The rule that runs get_filters safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 999md, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_filters, this is the rule to start with:
get_filters 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 999md, apply this rule, and every get_filters call is checked against it from then on.
Questions about get_filters
get_filters is a read tool on the 999md MCP server. It is categorised as a Read tool in the 999md MCP Server, which means it retrieves data without modifying state.
Register the 999md MCP server in PolicyLayer and add a rule for get_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 999md. Nothing to install.
get_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 get_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 get_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.
get_filters is provided by the 999md MCP server (ilodezis/999md-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 999md, and thousands of servers like it.
This server
Across the catalogue