// SCAN REPORT

Freshservice MCP Server

53 tools. 24 can modify or destroy data without limits.

7 destructive tools with no built-in limits. Policy required.

Last updated: 30 Jun 2026

24 can modify or destroy data

29 read-only

53 tools total

Community server · catalogue entry verified 30/06/2026

How to control Freshservice MCP Server ↓

TOOL MAP

What Freshservice MCP Server exposes to your agents

Read (29) Write / Execute (17) Destructive / Financial (7)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Freshservice MCP Server tools

Destructive · High delete_asset This tool irreversibly deletes data (an asset record) from the Freshservice system with no undo capability. Destructive · High delete_change Deleting a change request is a destructive operation that cannot be undone. Destructive · High delete_problem This tool permanently removes problem records from the Freshservice ITSM system without the ability to undo the action. Destructive · High delete_solution_article This tool performs an irreversible deletion operation on knowledge base content.

24 of Freshservice MCP Server's 53 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Freshservice MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and Freshservice MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "delete_asset": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "add_note_to_ticket": {
    "limits": [
      {
        "counter": "add_note_to_ticket_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_agent": {
    "limits": [
      {
        "counter": "get_agent_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Freshservice MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON FRESHSERVICE →

Instant setup, no code required.

FULL CATALOGUE

All 53 Freshservice MCP Server tools

DESTRUCTIVE 7 tools

Destructive delete_asset Delete a Freshservice asset Destructive delete_change Delete a Freshservice change request Destructive delete_problem Delete a Freshservice problem Destructive delete_solution_article Delete a knowledge base article Destructive delete_ticket Delete a Freshservice ticket (moves to trash) Destructive delete_ticket_task Delete a task from a Freshservice ticket Destructive delete_time_entry Delete a time entry from a Freshservice ticket

WRITE 17 tools

Write add_note_to_ticket Add a note to a Freshservice ticket Write create_asset Create a new Freshservice asset Write create_change Create a new Freshservice change request Write create_problem Create a new Freshservice problem Write create_solution_article Create a new knowledge base article Write create_ticket Create a new Freshservice ticket Write create_ticket_task Create a new task on a Freshservice ticket Write create_time_entry Log time spent on a Freshservice ticket Write place_service_request Place a service request from the Freshservice catalog Write reply_to_ticket Reply to a Freshservice ticket Write update_asset Update an existing Freshservice asset Write update_change Update an existing Freshservice change request Write update_problem Update an existing Freshservice problem Write update_solution_article Update an existing knowledge base article Write update_ticket Update an existing Freshservice ticket Write update_ticket_task Update a task on a Freshservice ticket Write update_time_entry Update a time entry on a Freshservice ticket

READ 29 tools

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Freshservice MCP Server

Can an AI agent delete data through the Freshservice MCP Server MCP server? +

Yes. The Freshservice MCP Server server exposes 7 destructive tools including delete_asset, delete_change, delete_problem. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Freshservice MCP Server? +

The Freshservice MCP Server server has 17 write tools including add_note_to_ticket, create_asset, create_change. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Freshservice MCP Server.

How many tools does the Freshservice MCP Server MCP server expose? +

53 tools across 3 categories: Destructive, Read, Write. 29 are read-only. 24 can modify, create, or delete data.

How do I enforce a policy on Freshservice MCP Server? +

Register the Freshservice MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Freshservice MCP Server tool call.

Deterministic rules across all 53 Freshservice MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON FRESHSERVICE →

Instant setup, no code required.

53 Freshservice MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.