update_security_case_evidence
Update an existing Security Case Evidence in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_security_case_evidence afterwards to see the updated record.
This record as markdown: /tools/com-oneuptime-mcp/update-security-case-evidence.md
What update_security_case_evidence does on OneUptime
AI agents use update_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 |
|---|---|---|---|
id | string | Yes | The unique identifier (UUID) of the Security Case Evidence to update. Required. Use list_security_case_evidence to find IDs. |
name | string | — | What the evidence is, in a few words. A file's own name when none is given. |
description | string | — | What the evidence shows, and where and how it was collected. |
Parameters from the server's own tool schema.
Why update_security_case_evidence is rated Medium
An AI agent can call update_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.
Attacks that exploit this kind of access
The rule that runs update_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 update_security_case_evidence, this is the rule to start with:
update_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.
The button opens the PolicyLayer dashboard: create your workspace, connect OneUptime, apply this rule, and every update_security_case_evidence call is checked against it from then on.
Questions about update_security_case_evidence
Update an existing Security Case Evidence in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_security_case_evidence 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.
update_security_case_evidence accepts 3 parameters: id, name, description. Required: id. 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 update_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.
update_security_case_evidence 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 update_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.
Set action: deny in the PolicyLayer policy for update_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.
update_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.
More on OneUptime, and thousands of servers like it.
This server
Across the catalogue