update_event

Update an existing calendar event.

SERVERFreshdesk SOURCE@mindstone-engineering/mcp-server-freshdesk

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/freshdesk/update-event.md

WHAT IT DOES

What update_event does on Freshdesk

AI agents use update_event to create or update resources in Freshdesk, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Freshdesk environment.

RISK

Why update_event is rated Medium

This tool modifies existing calendar event data in a reversible manner (updates can typically be undone by further updates or undo operations). It does not delete data (Destructive), execute arbitrary code (Execute), or involve financial transactions (Financial).

From the tool's definition Tool name is 'update_event' and description states 'Update an existing calendar event.' The verb 'update' indicates modification of existing data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_event safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Freshdesk, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_event, this is the rule to start with:

update_event Rate-limited

update_event 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_event": {
      "limits": [
        {
          "counter": "update_event_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Freshdesk, apply this rule, and every update_event call is checked against it from then on.

FAQ

Questions about update_event

What does the update_event tool do? +

Update an existing calendar event. It is categorised as a Write tool in the Freshdesk 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_event? +

Register the Freshdesk MCP server in PolicyLayer and add a rule for update_event: 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 Freshdesk. Nothing to install.

What risk level is update_event? +

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

Can I rate-limit update_event? +

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

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

update_event is provided by the Freshdesk MCP server (@mindstone-engineering/mcp-server-freshdesk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Freshdesk, and thousands of servers like it.

This server

All 422 Freshdesk tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP →calendar_create_event on Apple Apps MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →