Check if a URL is alive using ReviewWeb.site API.
AI agents call url_is_alive to retrieve information from ReviewWebsite MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that performs a health/availability check on a URL. It retrieves status information about whether a resource is reachable, with no side effects, no data modification, no code execution, and no destructive impact. The low severity reflects minimal blast radius—confirming a URL's liveness poses negligible risk even if misused by an AI agent.
From the tool's definition Tool name 'url_is_alive' and description 'Check if a URL is alive using ReviewWeb.site API' indicate a simple HTTP status check or connectivity test that queries external state without modifying, executing code, deleting, or moving money.
Documented attack patterns abuse exactly the kind of access url_is_alive gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ReviewWebsite MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for url_is_alive:
{
"version": "1",
"default": "deny",
"tools": {
"url_is_alive": {}
}
}url_is_alive is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check if a URL is alive using ReviewWeb.site API. It is categorised as a Read tool in the ReviewWebsite MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ReviewWebsite MCP Server MCP server in PolicyLayer and add a rule for url_is_alive: 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 ReviewWebsite MCP Server. Nothing to install.
url_is_alive 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 url_is_alive 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 url_is_alive. 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.
url_is_alive is provided by the ReviewWebsite MCP Server MCP server (mrgoonie/reviewwebsite-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ReviewWebsite MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
16 ReviewWebsite MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.