update_solution_category · Freshservice MCP Server MCP

WHAT IT DOES

What update_solution_category does on Freshservice MCP Server

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

This tool modifies configuration data (solution categories) within an IT service management platform. While reversible and not destructive, updating categories can affect solution organization, searchability, and visibility across the platform, potentially impacting multiple users and workflows.

From the tool's definition Tool description states it 'Update[s] a solution category' in Freshservice, which modifies existing data. The verb 'update' indicates reversible modification without deletion or financial impact.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_solution_category Rate-limited

update_solution_category 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_solution_category": {
      "limits": [
        {
          "counter": "update_solution_category_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_solution_category

What does the update_solution_category tool do? +

Update a solution category in Freshservice. 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_solution_category? +

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

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

Can I rate-limit update_solution_category? +

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

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

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