uptimerobot_get_monitors
List UptimeRobot monitors (signals when any are DOWN).
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/uptimerobot-get-monitors.md
What uptimerobot_get_monitors does on UnClick
AI agents call uptimerobot_get_monitors to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
search | string | — | Filter monitors by name or URL |
api_key | string | Yes | UptimeRobot API key |
Parameters from the server's own tool schema.
Why uptimerobot_get_monitors is rated Low
This tool queries and returns status information about monitoring endpoints. While it provides information about system downtime, it only reads/lists existing monitor data without modifying, deleting, executing code, or creating financial obligations. The informational nature of status signals makes this a straightforward Read operation with low severity.
From the tool's definition Tool name contains 'get' and description states 'List UptimeRobot monitors', which is a retrieval operation with no modification or side effects.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs uptimerobot_get_monitors safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For uptimerobot_get_monitors, this is the rule to start with:
uptimerobot_get_monitors is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every uptimerobot_get_monitors call is checked against it from then on.
Questions about uptimerobot_get_monitors
List UptimeRobot monitors (signals when any are DOWN). It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
uptimerobot_get_monitors accepts 2 parameters: search, api_key. Required: api_key. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for uptimerobot_get_monitors: 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 UnClick. Nothing to install.
uptimerobot_get_monitors is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the uptimerobot_get_monitors 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 uptimerobot_get_monitors. 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.
uptimerobot_get_monitors is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue