update_security_playbook

SERVEROneUptime SOURCEhttps://oneuptime.com/mcp

Medium RISK CLASS

Category Write

Parameters 91 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-oneuptime-mcp/update-security-playbook.md

WHAT IT DOES

What update_security_playbook does on OneUptime

AI agents use update_security_playbook to create or update resources in OneUptime, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OneUptime environment.

Parameter	Type	Required	Description
`id`	string	Yes	The unique identifier (UUID) of the Security Playbook to update. Required. Use list_security_playbooks to find IDs.
`name`	object	—	What the playbook does, in a few words.
`steps`	object	—	The steps the playbook takes, in order. Each has an action, its settings, and whether it needs approval, may fail without stopping the run, or runs only when th
`trigger`	string	—	When the playbook runs on its own: Case Opened, Detection Added (a new detection joins an open case), or Manual (only when somebody runs it).
`isEnabled`	boolean	—	Whether the playbook runs on its own. A disabled playbook can still be run by hand from a case.
`description`	string	—	When to use the playbook and what it is for.
`detectionSource`	string	—	Run only on cases raised by this source: a Detection Rule, Threat Intel, a Connected Product or Entity Risk. Empty runs on every source.
`detectionRuleIds`	object	—	Run only on cases with a detection from one of these detection rules. Empty runs on cases from any rule.
`minimumSecurityCasePriorityId`	string	—	ID of the lowest case priority the playbook runs on by itself. Empty runs on every priority.

Parameters from the server's own tool schema.

RISK

Why update_security_playbook is rated Medium

An AI agent can call update_security_playbook faster than any human can review: one bad instruction and it creates or modifies resources in OneUptime by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_security_playbook safely

PolicyLayer is an MCP gateway: it sits between your AI agents and OneUptime, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_security_playbook, this is the rule to start with:

update_security_playbook Rate-limited

update_security_playbook 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": {
    "update_security_playbook": {
      "limits": [
        {
          "counter": "update_security_playbook_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect OneUptime, apply this rule, and every update_security_playbook call is checked against it from then on.

FAQ

Questions about update_security_playbook

What does the update_security_playbook tool do? +

Update an existing Security Playbook in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_security_playbook afterwards to see the updated record. It is categorised as a Write tool in the OneUptime MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does update_security_playbook accept? +

update_security_playbook accepts 9 parameters: id, name, steps, trigger, isEnabled, description, detectionSource, detectionRuleIds, minimumSecurityCasePriorityId. Required: id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_security_playbook? +

Register the OneUptime MCP server in PolicyLayer and add a rule for update_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 OneUptime. Nothing to install.

What risk level is update_security_playbook? +

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

Can I rate-limit update_security_playbook? +

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

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

update_security_playbook is provided by the OneUptime MCP server (https://oneuptime.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on OneUptime, and thousands of servers like it.

This server

All 223 OneUptime tools →

Across the catalogue

platform_security_review on 05 Mcp A2a Solution Studio →aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →