monitor_runs

List monitor runs HTTP: GET /v1/monitors/{id}/runs

SERVERReplyNodes SOURCEhttps://mcp.replynodes.com/mcp

Low RISK CLASS

Category Read

Parameters 31 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/com-replynodes-mcp/monitor-runs.md

WHAT IT DOES

What monitor_runs does on ReplyNodes

AI agents call monitor_runs to retrieve information from ReplyNodes 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
`id`	string	Yes	path parameter
`limit`	integer	—	query parameter
`cursor`	string	—	query parameter

Parameters from the server's own tool schema.

RISK

Why monitor_runs is rated Low

Tool retrieves historical monitor run data without modification or side effects.

From the tool's definition List monitor runs, GET request, retrieves monitoring data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs monitor_runs safely

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

monitor_runs Allowed

monitor_runs 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_runs": {}
  }
}

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

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

FAQ

Questions about monitor_runs

What does the monitor_runs tool do? +

List monitor runs HTTP: GET /v1/monitors/{id}/runs. It is categorised as a Read tool in the ReplyNodes MCP Server, which means it retrieves data without modifying state.

What parameters does monitor_runs accept? +

monitor_runs accepts 3 parameters: id, limit, cursor. 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_runs? +

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

What risk level is monitor_runs? +

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

Can I rate-limit monitor_runs? +

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

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

monitor_runs is provided by the ReplyNodes MCP server (https://mcp.replynodes.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ReplyNodes, and thousands of servers like it.

This server

All 66 ReplyNodes tools →

Across the catalogue

The MCP Attack Database →

Guides

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