send_change_approval_reminder · Freshservice MCP Server MCP

WHAT IT DOES

What send_change_approval_reminder does on Freshservice MCP Server

AI agents invoke send_change_approval_reminder to trigger actions in Freshservice MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why send_change_approval_reminder needs a policy

Sending a reminder is an external operation that triggers notifications to other users/systems. It doesn't merely read or write data in a reversible way, but actively triggers an external communication event. It falls under Execute as it initiates an external operation whose effect (sending the reminder) depends on the change approval context.

From the tool's definition 'Send reminder for a change approval' — triggers an external notification/communication action to approval participants

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

send_change_approval_reminder Rate-limited

send_change_approval_reminder stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "send_change_approval_reminder": {
      "limits": [
        {
          "counter": "send_change_approval_reminder_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 send_change_approval_reminder

What does the send_change_approval_reminder tool do? +

Send reminder for a change approval. It is categorised as a Execute tool in the Freshservice MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on send_change_approval_reminder? +

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

send_change_approval_reminder is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit send_change_approval_reminder? +

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

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

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