update_solution_folder · Freshservice MCP Server MCP

WHAT IT DOES

What update_solution_folder does on Freshservice MCP Server

AI agents use update_solution_folder 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_folder needs a policy

This tool modifies configuration/organizational data within Freshservice (updating folder properties) but does not delete data, execute arbitrary code, or move money. It is reversible—updates can be corrected by subsequent updates. The blast radius is limited to solution folder organization and visibility, affecting documentation management but not critical operational systems like tickets or change approvals.

From the tool's definition Tool name 'update_solution_folder' and description 'Update an existing solution folder's details' indicate modification of existing data (solution folder metadata) in the Freshservice platform.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_solution_folder Rate-limited

update_solution_folder 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_folder": {
      "limits": [
        {
          "counter": "update_solution_folder_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_folder

What does the update_solution_folder tool do? +

Update an existing solution folder's details 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_folder? +

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

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

Can I rate-limit update_solution_folder? +

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

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

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