Skip to main content
Glama

run_security_playbook

Executes a security response playbook against a specified incident to automate response actions, with optional background execution and input parameters.

Instructions

Execute a security response playbook against an incident. [Write]

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "playbook_sys_id": "<playbook_sys_id>",
      "incident_sys_id": "<incident_sys_id>"
    },
    "name": "run_security_playbook"
  }
}

Input Schema

NameRequiredDescriptionDefault
asyncNoRun as a background job and return a job_id at once. Poll it with get_job. Calls that take longer than about 20 seconds switch to a job on their own.
parametersNoOptional playbook input parameters
incident_sys_idYesSecurity incident sys_id to run against
playbook_sys_idYesPlaybook sys_id to execute

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.0.1
    • addedInput schema / properties / async
      Added value: +{
      +  "description": "Run as a background job and return a job_id at once. Poll it with get_job. Calls that take longer than about 20 seconds switch to a job on their own.",
      +  "type": "boolean"
      +}
  2. First observedv1.0.2

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The '[Write]' tag only restates readOnlyHint=false, and the annotations already declare non-idempotent, non-destructive, open-world behavior. Nothing is said about what the playbook does to the incident, whether repeated runs create multiple executions, or that the call may be long-running; the async/polling behavior lives only in the schema, not the description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One tight sentence with the action front-loaded and no filler. The bolded '[Write]' marker is redundant given the annotations, but the overall structure is efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a non-idempotent, open-world write that kicks off a multi-step playbook, yet the description says nothing about side effects, expected duration, or what an execution returns (execution record vs. job_id). With no output schema, the description should carry more of that burden.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the async parameter is documented with polling guidance and the ~20 second auto-switch behavior. The description adds no parameter meaning beyond that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Execute a security response playbook') plus the target ('against an incident'), so an agent can tell what the tool does. It does not differentiate itself from the close sibling execute_playbook, which leaves ambiguity about which execution tool to choose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use, when-not-to-use, or prerequisite guidance. Nothing tells the agent when to pick this over execute_playbook or create_playbook, nor what needs to exist first (a listed playbook and an existing incident sys_id).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools