create_security_playbook
Create a new Security Playbook in OneUptime. Returns the created Security Playbook object with its ID. Use this to add new Security Playbooks to your project. Note: projectId is inferred from your API key — you do not need to provide it.
This record as markdown: /tools/com-oneuptime-mcp/create-security-playbook.md
What create_security_playbook does on OneUptime
AI agents use create_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 |
|---|---|---|---|
name | object | Yes | 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. |
projectId | string | — | ID of the project this playbook belongs to. |
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.
Why create_security_playbook is rated Medium
An AI agent can call create_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
The rule that runs create_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 create_security_playbook, this is the rule to start with:
create_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.
The button opens the PolicyLayer dashboard: create your workspace, connect OneUptime, apply this rule, and every create_security_playbook call is checked against it from then on.
Questions about create_security_playbook
Create a new Security Playbook in OneUptime. Returns the created Security Playbook object with its ID. Use this to add new Security Playbooks to your project. Note: projectId is inferred from your API key — you do not need to provide it. 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.
create_security_playbook accepts 9 parameters: name, steps, trigger, isEnabled, projectId, description, detectionSource, detectionRuleIds, minimumSecurityCasePriorityId. Required: name. The full parameter table on this page comes from the server's own tool schema.
Register the OneUptime MCP server in PolicyLayer and add a rule for create_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.
create_security_playbook 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 create_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.
Set action: deny in the PolicyLayer policy for create_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.
create_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.
More on OneUptime, and thousands of servers like it.
This server
Across the catalogue