create_incident_internal_note

SERVEROneUptime SOURCEhttps://oneuptime.com/mcp

Medium RISK CLASS

Category Write

Parameters 61 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-oneuptime-mcp/create-incident-internal-note.md

WHAT IT DOES

What create_incident_internal_note does on OneUptime

AI agents use create_incident_internal_note 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
`note`	string	—	Notes in markdown.
`postedAt`	object	—	Date and time the note belongs to in the timeline: when it was written, or - for a note saved from a Slack or Microsoft Teams message - when that message was po
`projectId`	string	—	ID of your OneUptime Project in which this object belongs.
`incidentId`	string	Yes	Relation to Incident ID in which this resource belongs.
`attachments`	array	—	Files attached to this note.
`postedFromSlackMessageId`	string	—	Unique identifier for the Slack message this note was created from (channel_id:message_ts). Used to prevent duplicate notes when multiple users react to the sam

Parameters from the server's own tool schema.

RISK

Why create_incident_internal_note is rated Medium

An AI agent can call create_incident_internal_note 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 create_incident_internal_note 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_incident_internal_note, this is the rule to start with:

create_incident_internal_note Rate-limited

create_incident_internal_note 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": {
    "create_incident_internal_note": {
      "limits": [
        {
          "counter": "create_incident_internal_note_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 create_incident_internal_note call is checked against it from then on.

FAQ

Questions about create_incident_internal_note

What does the create_incident_internal_note tool do? +

Create a new Incident Internal Note in OneUptime. Returns the created Incident Internal Note object with its ID. Use this to add new Incident Internal Notes 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.

What parameters does create_incident_internal_note accept? +

create_incident_internal_note accepts 6 parameters: note, postedAt, projectId, incidentId, attachments, postedFromSlackMessageId. Required: incidentId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on create_incident_internal_note? +

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

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

Can I rate-limit create_incident_internal_note? +

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

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

create_incident_internal_note 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

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

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