update_problem
Update fields on an existing problem (requires WRITE_ENABLED=true)
This record as markdown: /tools/servicenow-mcp-server/update-problem.md
What update_problem does on ServiceNow MCP Server
AI agents use update_problem to create or update resources in ServiceNow MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ServiceNow MCP Server environment.
Why update_problem is rated Medium
This tool creates or modifies data reversibly by updating problem records. While it affects existing data, updates are typically reversible (prior values can be restored), distinguishing it from destructive operations. The high severity reflects that problems in ServiceNow often track critical incidents and security issues, so unauthorized or erroneous updates could cause significant operational impact.
From the tool's definition Tool description explicitly states 'Update fields on an existing problem' and requires 'WRITE_ENABLED=true', indicating it modifies existing data in ServiceNow.
Attacks that exploit this kind of access
The rule that runs update_problem safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ServiceNow MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_problem, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect ServiceNow MCP Server, apply this rule, and every update_problem call is checked against it from then on.
Questions about update_problem
Update fields on an existing problem (requires WRITE_ENABLED=true). It is categorised as a Write tool in the ServiceNow MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ServiceNow 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 ServiceNow MCP Server. Nothing to install.
update_problem is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
update_problem is provided by the ServiceNow MCP Server MCP server (@aartiq/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ServiceNow MCP Server, and thousands of servers like it.
This server
Across the catalogue