set_remediation_commitment
Set the remediation commitment / target date on a Vulnerable Item (remediation_commitment_dt_tm)
This record as markdown: /tools/tedorigawa001-servicenow-mcp/set-remediation-commitment.md
What set_remediation_commitment does on ServiceNow-MCP
AI agents use set_remediation_commitment 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.
Why set_remediation_commitment is rated Medium
This tool creates or modifies data (the remediation commitment date) in a reversible manner. It does not execute code, delete data, or move money. While it affects security-related records in a vulnerability management context, the action itself is a standard Write operation—the date can be updated again or cleared.
From the tool's definition Tool sets (modifies) the remediation_commitment_dt_tm field on a Vulnerable Item, which is a reversible data update operation. Description explicitly states 'Set the remediation commitment / target date' indicating modification of an existing record.
Attacks that exploit this kind of access
The rule that runs set_remediation_commitment safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ServiceNow-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_remediation_commitment, this is the rule to start with:
set_remediation_commitment 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, apply this rule, and every set_remediation_commitment call is checked against it from then on.
Questions about set_remediation_commitment
Set the remediation commitment / target date on a Vulnerable Item (remediation_commitment_dt_tm). 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 set_remediation_commitment: 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.
set_remediation_commitment 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 set_remediation_commitment 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 set_remediation_commitment. 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.
set_remediation_commitment 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.
More on ServiceNow, and thousands of servers like it.
This server
Across the catalogue