monitor_list

List every uptime monitor with state, streak, interval, and last-check timestamp.

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What monitor_list does on Yaver

AI agents call monitor_list to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why monitor_list is rated Low

The tool retrieves and displays monitoring metadata (state, streak, interval, timestamps) without modifying, executing, or deleting any data. This is a straightforward read/query operation. Severity is low because the exposed information is monitoring status metadata with minimal blast radius even if misused by an agent.

From the tool's definition Tool name is 'monitor_list' and description states it 'List[s] every uptime monitor with state, streak, interval, and last-check timestamp' — a purely informational retrieval action with no mutations or side effects.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

monitor_list Allowed

monitor_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "monitor_list": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about monitor_list

What does the monitor_list tool do? +

List every uptime monitor with state, streak, interval, and last-check timestamp. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on monitor_list? +

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

monitor_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit monitor_list? +

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

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

monitor_list 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 →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →