get_filters
AI agents call get_filters to retrieve information from Pipedrive MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
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
get_filters. It is categorised as a Read tool in the Pipedrive MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Pipedrive MCP Server 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 Pipedrive MCP Server. 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 Pipedrive MCP Server MCP server (osherai/pipedrive-mcp-python). 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 →