update_problem · Freshservice MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_problem does on Freshservice MCP Server

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

This tool modifies existing problem records within Freshservice ITSM, which is a write operation. It updates data reversibly (changes can be corrected or reverted through subsequent updates), making it Write rather than Destructive. The medium severity reflects that misuse could corrupt problem records and impact incident management workflows, but changes are not permanent.

From the tool's definition Tool name 'update_problem' and description 'Update an existing Freshservice problem' indicate modification of existing data in a reversible manner.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_problem Rate-limited

update_problem 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_problem": {
      "limits": [
        {
          "counter": "update_problem_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_problem

What does the update_problem tool do? +

Update an existing Freshservice problem. 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_problem? +

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

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

Can I rate-limit update_problem? +

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

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

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