update_approval_chain_rule_change

WHAT IT DOES

What update_approval_chain_rule_change does on Freshservice MCP Server

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

This tool modifies approval chain rules, which are configuration policies that govern how change requests are validated and approved within an IT service management system. Misuse could allow an AI agent to alter approval workflows to bypass security controls, suppress notifications, or redirect approvals to unintended parties, potentially enabling unauthorized changes.

From the tool's definition Tool name contains 'update' and description states 'Update approval chain rule for a change.' The verb 'update' indicates modification of existing data (approval chain rules) rather than creation or deletion.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_approval_chain_rule_change Rate-limited

update_approval_chain_rule_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_approval_chain_rule_change": {
      "limits": [
        {
          "counter": "update_approval_chain_rule_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_approval_chain_rule_change

What does the update_approval_chain_rule_change tool do? +

Update approval chain rule for a change. 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_approval_chain_rule_change? +

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

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

Can I rate-limit update_approval_chain_rule_change? +

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

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

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