create_requester_group · Freshservice MCP Server MCP

WHAT IT DOES

What create_requester_group does on Freshservice MCP Server

AI agents use create_requester_group to create or update resources in Freshservice MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Freshservice MCP Server environment.

WHY IT NEEDS A POLICY

Why create_requester_group needs a policy

This tool creates new organizational structures (requester groups) within an IT service management system. It is a Write operation—reversible through deletion—not a Read (no data retrieval), Execute (no arbitrary code/script execution), Destructive (group can be deleted), or Financial operation.

From the tool's definition Tool name 'create_requester_group' and description 'Create a requester group in Freshservice' directly indicate data creation. Server context shows this is part of Freshservice IT service management platform where groups organize users/requesters.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_requester_group Rate-limited

create_requester_group stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_requester_group": {
      "limits": [
        {
          "counter": "create_requester_group_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Freshservice MCP Server, so you can run agents against it safely.

FAQ

Questions about create_requester_group

What does the create_requester_group tool do? +

Create a requester group in Freshservice. It is categorised as a Write tool in the Freshservice MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_requester_group? +

Register the Freshservice MCP Server MCP server in PolicyLayer and add a rule for create_requester_group: 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.

What risk level is create_requester_group? +

create_requester_group is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_requester_group? +

Yes. Add a rate_limit block to the create_requester_group 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.

How do I block create_requester_group completely? +

Set action: deny in the PolicyLayer policy for create_requester_group. 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.

What MCP server provides create_requester_group? +

create_requester_group 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.