New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

monitor_add

Register a new uptime monitor for a URL. The agent probes every interval; three consecutive failures fire a push alert.

SERVERYaver SOURCEyaver-cli
Medium RISK CLASS
Category Write
Parameters 41 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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

What monitor_add does on Yaver

AI agents use monitor_add to create or update resources in Yaver, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yaver environment.

ParameterTypeRequiredDescription
url string Yes
name string
method string HTTP method, default GET
interval string Go duration, e.g. 60s, 5m

Parameters from the server's own tool schema.

Why monitor_add is rated Medium

This tool creates a new monitoring resource (registering a monitor), which is a reversible write operation. It does not execute code, delete data, or move money. Misuse could result in unwanted monitors being created or alerts being fired, but the blast radius is moderate.

From the tool's definition Register a new uptime monitor for a URL

Risk signalsAccepts URL/endpoint input (url) · Bulk/mass operation — affects multiple targets

Questions about monitor_add

What does the monitor_add tool do? +

Register a new uptime monitor for a URL. The agent probes every interval; three consecutive failures fire a push alert. It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does monitor_add accept? +

monitor_add accepts 4 parameters: url, name, method, interval. Required: url. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on monitor_add? +

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

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

Can I rate-limit monitor_add? +

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

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

monitor_add 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.

More on Yaver, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Yaver's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.