Update a Remediation Task by sys_id (state, assignee, group, target date, etc.).
AI agents use update_remediation_task to create or update resources in ServiceNow-MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ServiceNow-MCP environment.
This tool creates or modifies data reversibly within ServiceNow's remediation task system. Updates to task state, assignee, group, and target date are standard data modifications that can be undone or corrected through subsequent updates.
From the tool's definition Tool description states 'Update a Remediation Task by sys_id (state, assignee, group, target date, etc.)', which modifies existing records with fields like state, assignee, group, and target date.
Attacks that exploit this kind of access
Update a Remediation Task by sys_id (state, assignee, group, target date, etc.). It is categorised as a Write tool in the ServiceNow-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ServiceNow- MCP server in PolicyLayer and add a rule for update_remediation_task: 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. Nothing to install.
update_remediation_task 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_remediation_task 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_remediation_task. 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_remediation_task is provided by the ServiceNow- MCP server (tedorigawa001/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →