close_change · Freshservice MCP Server MCP: Risk & Policy

WHAT IT DOES

What close_change does on Freshservice MCP Server

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

Closing a change modifies its state and typically marks it as complete, which is a write operation. While the effect is significant in a workflow context (blocking further modifications), the action itself is theoretically reversible (changes can be reopened in most ITSM systems). This is categorized as Write rather than Destructive because it does not irreversibly delete or purge data.

From the tool's definition Tool name 'close_change' and description 'Close a change' indicates modification of a change record's status to a terminal/closed state. This is a reversible state change operation on an existing entity in the IT service management system, not deletion.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

close_change Rate-limited

close_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": {
    "close_change": {
      "limits": [
        {
          "counter": "close_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 close_change

What does the close_change tool do? +

Close a change and provide the result explanation. 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 close_change? +

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

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

Can I rate-limit close_change? +

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

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

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