run_security_playbook · ServiceNow- MCP: Risk & Policy

WHAT IT DOES

What run_security_playbook does on ServiceNow-MCP

AI agents invoke run_security_playbook to trigger actions in ServiceNow-MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why run_security_playbook needs a policy

Although labeled [Write], this tool executes security response automation against incidents. Execution of security playbooks can trigger cascading effects including system changes, network actions, access modifications, or alerts depending on playbook definitions.

From the tool's definition Tool description states 'Execute a security response playbook against an incident.' The verb 'Execute' combined with 'playbook' indicates triggering external operations and automation workflows.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_security_playbook Rate-limited

run_security_playbook stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_security_playbook": {
      "limits": [
        {
          "counter": "run_security_playbook_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 run_security_playbook

What does the run_security_playbook tool do? +

Execute a security response playbook against an incident. [Write]. It is categorised as a Execute tool in the ServiceNow-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_security_playbook? +

Register the ServiceNow- MCP server in PolicyLayer and add a rule for run_security_playbook: 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 run_security_playbook? +

run_security_playbook is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_security_playbook? +

Yes. Add a rate_limit block to the run_security_playbook 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 run_security_playbook completely? +

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

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