Filter Freshservice agents based on a query.
AI agents call filter_agents to retrieve information from Freshservice 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 or searches agent records without creating, modifying, deleting, or executing operations. It has no side effects beyond returning filtered data. The blast radius of misuse is minimal—an AI agent querying agent information poses negligible risk compared to tools that modify tickets, create changes, or manage approvals visible in the sibling tool list.
From the tool's definition Tool name 'filter_agents' and description 'Filter Freshservice agents based on a query' indicate data retrieval with no modification or execution. The verb 'filter' combined with 'based on a query' suggests querying/searching agent records.
Attacks that exploit this kind of access
Filter Freshservice agents based on a query. It is categorised as a Read tool in the Freshservice MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Freshservice MCP Server MCP server in PolicyLayer and add a rule for filter_agents: 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 Freshservice MCP Server. Nothing to install.
filter_agents 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 filter_agents 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 filter_agents. 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.
filter_agents is provided by the Freshservice MCP Server MCP server (leemangold/freshservice_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 →