update_servicenow_incident

Update an existing incident in ServiceNow by sys_id.

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-servicenow-incident.md

What update_servicenow_incident does on Freshdesk

AI agents use update_servicenow_incident 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.

Why update_servicenow_incident is rated Medium

The tool modifies incident records in ServiceNow, a critical business system. This is a reversible Write operation (incidents can be updated again or reverted), but affects operational data in a system that organizations depend on for incident tracking and management.

From the tool's definition Tool name 'update_servicenow_incident' and description 'Update an existing incident in ServiceNow by sys_id' indicate modification of existing data in an external ticketing system.

Questions about update_servicenow_incident

What does the update_servicenow_incident tool do? +

Update an existing incident in ServiceNow by sys_id. 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_servicenow_incident? +

Register the Freshdesk MCP server in PolicyLayer and add a rule for update_servicenow_incident: 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_servicenow_incident? +

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

Can I rate-limit update_servicenow_incident? +

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

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

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

More on Freshdesk, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Freshdesk's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.