monitor_remove

Delete an uptime monitor by id or name.

SERVERYaver SOURCEyaver-cli

Critical RISK CLASS

Category Destructive

Parameters 11 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/monitor-remove.md

WHAT IT DOES

What monitor_remove does on Yaver

AI agents call monitor_remove to permanently remove resources in Yaver, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Parameter	Type	Required	Description
`id`	string	Yes

Parameters from the server's own tool schema.

RISK

Why monitor_remove is rated Critical

The tool permanently deletes an uptime monitor, which is an irreversible destructive action. Misuse by an AI agent could silently remove monitoring coverage, leaving services unobserved and outages undetected.

From the tool's definition 'Delete an uptime monitor by id or name' — explicitly deletes a resource irreversibly

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs monitor_remove safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For monitor_remove, this is the rule to start with:

monitor_remove Hidden

monitor_remove is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "monitor_remove"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every monitor_remove call is checked against it from then on.

FAQ

Questions about monitor_remove

What does the monitor_remove tool do? +

Delete an uptime monitor by id or name. It is categorised as a Destructive tool in the Yaver MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does monitor_remove accept? +

monitor_remove accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on monitor_remove? +

Register the Yaver MCP server in PolicyLayer and add a rule for monitor_remove: 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 Yaver. Nothing to install.

What risk level is monitor_remove? +

monitor_remove is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit monitor_remove? +

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

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

monitor_remove is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools → Critical-risk tools on this server →

Across the catalogue

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →