create_security_case
Create a new Security Case in OneUptime. Returns the created Security Case object with its ID. Use this to add new Security Cases 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-case.md
What create_security_case does on OneUptime
AI agents use create_security_case 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 |
|---|---|---|---|
title | string | Yes | What the case is about, in a line. |
labels | array | — | Labels to filter and report on cases by. |
verdict | string | — | What the case turned out to be, set when it is closed: True Positive, Benign Positive, False Positive or Undetermined. |
entities | object | — | The users, hosts, IP addresses, domains and files the case is about, each as { type, value }. Detections add theirs as they join the case. |
projectId | string | — | ID of the project this case belongs to. |
closingNote | string | — | Why the case was closed the way it was, in Markdown: what was found and what was done. |
description | string | — | What is known about the threat, in Markdown. A case opened by a detection starts with the detection's description. |
mitreTactics | object | — | ATT&CK tactic ids (TA0006) the case's detections are tagged with. |
mitreTechniques | object | — | ATT&CK technique ids (T1110) the case's detections are tagged with. |
assignedToTeamId | string | — | ID of the team whose queue the case is in. |
assignedToUserId | string | — | ID of the person working the case. |
securityCaseStatusId | string | — | ID of the case's status. Optional on create: a new case starts in the project's new status. |
Parameters from the server's own tool schema.
Why create_security_case is rated Medium
An AI agent can call create_security_case 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.
Risk signalsHigh parameter count (14 properties)
Attacks that exploit this kind of access
The rule that runs create_security_case 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_case, this is the rule to start with:
create_security_case 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_case call is checked against it from then on.
Questions about create_security_case
Create a new Security Case in OneUptime. Returns the created Security Case object with its ID. Use this to add new Security Cases 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_case accepts 12 parameters: title, labels, verdict, entities, projectId, closingNote, description, mitreTactics, mitreTechniques, assignedToTeamId, assignedToUserId, securityCaseStatusId. Required: title. 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_case: 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_case 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_case 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_case. 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_case 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