get_fetcher_readyz
Readiness (auth/db status) HTTP: GET /fetcher/readyz
This record as markdown: /tools/com-replynodes-mcp/get-fetcher-readyz.md
What get_fetcher_readyz does on ReplyNodes
AI agents call get_fetcher_readyz 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.
Why get_fetcher_readyz is rated Low
Health check endpoint returns system status without data retrieval or side effects.
From the tool's definition Readiness check; auth/db status query only.
Attacks that exploit this kind of access
The rule that runs get_fetcher_readyz 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 get_fetcher_readyz, this is the rule to start with:
get_fetcher_readyz 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 ReplyNodes, apply this rule, and every get_fetcher_readyz call is checked against it from then on.
Questions about get_fetcher_readyz
Readiness (auth/db status) HTTP: GET /fetcher/readyz. It is categorised as a Read tool in the ReplyNodes MCP Server, which means it retrieves data without modifying state.
Register the ReplyNodes MCP server in PolicyLayer and add a rule for get_fetcher_readyz: 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.
get_fetcher_readyz 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 get_fetcher_readyz 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 get_fetcher_readyz. 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.
get_fetcher_readyz 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.
More on ReplyNodes, and thousands of servers like it.
This server
Across the catalogue