create_security_case_evidence

SERVEROneUptime SOURCEhttps://oneuptime.com/mcp

Medium RISK CLASS

Category Write

Parameters 73 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-security-case-evidence.md

WHAT IT DOES

What create_security_case_evidence does on OneUptime

AI agents use create_security_case_evidence 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
`url`	string	—	Where the evidence is kept, for Link evidence: an http or https address.
`kind`	string	Yes	What the evidence is: a File uploaded to OneUptime, or a Link to evidence kept somewhere else. It can't be changed.
`name`	string	Yes	What the evidence is, in a few words. A file's own name when none is given.
`fileId`	string	—	ID of the uploaded file, for File evidence: upload it first, then name it here.
`projectId`	string	—	ID of the project this evidence belongs to.
`description`	string	—	What the evidence shows, and where and how it was collected.
`securityCaseId`	string	Yes	ID of the case this evidence is kept on.

Parameters from the server's own tool schema.

RISK

Why create_security_case_evidence is rated Medium

An AI agent can call create_security_case_evidence 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 signalsAccepts URL/endpoint input (url)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs create_security_case_evidence 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_evidence, this is the rule to start with:

create_security_case_evidence Rate-limited

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

FAQ

Questions about create_security_case_evidence

What does the create_security_case_evidence tool do? +

Create a new Security Case Evidence in OneUptime. Returns the created Security Case Evidence object with its ID. Use this to add new Security Case Evidence 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_security_case_evidence accept? +

create_security_case_evidence accepts 7 parameters: url, kind, name, fileId, projectId, description, securityCaseId. Required: kind, name, securityCaseId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on create_security_case_evidence? +

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

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

Can I rate-limit create_security_case_evidence? +

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

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

create_security_case_evidence 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 →create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server → The MCP Attack Database →

Guides

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