Get requester groups in Freshservice.
AI agents call get_requester_groups_by_id 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 queries and retrieves existing requester group data from Freshservice without modifying, executing, or destructively affecting any resources. It poses minimal risk as it only exposes group metadata that would typically be accessible to authenticated users with read permissions in the system.
From the tool's definition Tool name 'get_requester_groups_by_id' with description 'Get requester groups in Freshservice' indicates a retrieval operation. The 'get' verb and absence of modifying language (create, update, delete) confirm read-only access to group information.
Attacks that exploit this kind of access
Get requester groups in Freshservice. 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 get_requester_groups_by_id: 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.
get_requester_groups_by_id 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_requester_groups_by_id 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_requester_groups_by_id. 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_requester_groups_by_id 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 →