add_vi_to_remediation_task · ServiceNow- MCP: Risk & Policy

WHAT IT DOES

What add_vi_to_remediation_task does on ServiceNow-MCP

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

WHY IT NEEDS A POLICY

Why add_vi_to_remediation_task needs a policy

This tool modifies relationships within the CMDB/vulnerability management system by associating vulnerable items with remediation tasks. While reversible (the association can be removed), it has medium severity because misconfiguration could direct remediation efforts toward wrong targets or create false associations in a critical security workflow.

From the tool's definition Tool name 'add_vi_to_remediation_task' and description 'Associate a Vulnerable Item with a remediation group' indicate the tool creates or modifies an association between entities in ServiceNow.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_vi_to_remediation_task Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_vi_to_remediation_task": {
      "limits": [
        {
          "counter": "add_vi_to_remediation_task_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches ServiceNow-MCP, so you can run agents against it safely.

FAQ

Questions about add_vi_to_remediation_task

What does the add_vi_to_remediation_task tool do? +

Associate a Vulnerable Item with a remediation group via the. 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.

How do I enforce a policy on add_vi_to_remediation_task? +

Register the ServiceNow- MCP server in PolicyLayer and add a rule for add_vi_to_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.

What risk level is add_vi_to_remediation_task? +

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

Can I rate-limit add_vi_to_remediation_task? +

Yes. Add a rate_limit block to the add_vi_to_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.

How do I block add_vi_to_remediation_task completely? +

Set action: deny in the PolicyLayer policy for add_vi_to_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.

What MCP server provides add_vi_to_remediation_task? +

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