HTTP ping to check if a site is reachable and measure response time.
AI agents call check_uptime to retrieve information from SiteHealth MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves monitoring data about website availability and latency. It sends HTTP requests to measure response times but does not modify any state, execute code on the target, or trigger side effects. It is purely informational/observational, fitting the Read category. Severity is low because misuse would only generate harmless HTTP requests and expose publicly available uptime/performance information.
From the tool's definition Tool performs 'HTTP ping to check if a site is reachable and measure response time' — a passive query operation with no data modification, creation, deletion, or external state change.
Attacks that exploit this kind of access
HTTP ping to check if a site is reachable and measure response time. It is categorised as a Read tool in the SiteHealth MCP MCP Server, which means it retrieves data without modifying state.
Register the SiteHealth MCP server in PolicyLayer and add a rule for check_uptime: 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 SiteHealth MCP. Nothing to install.
check_uptime 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 check_uptime 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 check_uptime. 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.
check_uptime is provided by the SiteHealth MCP server (sitehealth-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →