update_change · Freshservice MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_change does on Freshservice MCP Server

AI agents use update_change 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 update_change needs a policy

The tool performs a write operation by updating change request data in Freshservice. While changes can have operational impact, the update itself is reversible (can be changed again or reverted). This is less severe than destructive operations (which cannot be undone) but more risky than simple reads.

From the tool's definition Tool name is 'update_change' and description states 'Update an existing Freshservice change request' — this modifies an existing record reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_change Rate-limited

update_change 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": {
    "update_change": {
      "limits": [
        {
          "counter": "update_change_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 update_change

What does the update_change tool do? +

Update an existing Freshservice change request. 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 update_change? +

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

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

Can I rate-limit update_change? +

Yes. Add a rate_limit block to the update_change 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 update_change completely? +

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

update_change is provided by the Freshservice MCP Server MCP server (tannertm0/freshservice-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.