update_problem
Update fields on an existing problem (requires WRITE_ENABLED=true)
This record as markdown: /tools/nowaikit-servicenow-ai-toolkit/update-problem.md
What update_problem does on NowAIKit — ServiceNow AI Toolkit
AI agents use update_problem to create or update resources in NowAIKit — ServiceNow AI Toolkit, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your NowAIKit — ServiceNow AI Toolkit environment.
Why update_problem is rated Medium
This tool creates or modifies data in a reversible manner by updating problem fields in ServiceNow. Updates are non-destructive and can typically be undone or overwritten. The medium severity reflects that misconfiguration or agent error could modify critical incident/problem records, potentially affecting operational visibility and tracking, but the action is reversible.
From the tool's definition Tool name 'update_problem' combined with description 'Update fields on an existing problem' indicates modification of existing data. The description explicitly notes 'requires WRITE_ENABLED=true', confirming write-level access.
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 NowAIKit — ServiceNow AI Toolkit, 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 NowAIKit — ServiceNow AI Toolkit, 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 NowAIKit — ServiceNow AI Toolkit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the NowAIKit — ServiceNow AI Toolkit 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 NowAIKit — ServiceNow AI Toolkit. 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 NowAIKit — ServiceNow AI Toolkit MCP server (nowaikit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on NowAIKit — ServiceNow AI Toolkit, and thousands of servers like it.
This server
Across the catalogue