checkWebsiteStatus

Check if a URL is accessible without downloading the content

Server Advanced Web Fetching MCP Server llmbaseai/mcp-servers
Category Read
Risk class Low
Parameters 00 required

What checkWebsiteStatus does on Advanced Web Fetching MCP Server

AI agents call checkWebsiteStatus to retrieve information from Advanced Web Fetching MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why checkWebsiteStatus needs a policy

The tool queries the availability/status of a URL but explicitly avoids downloading content. This is a read-only operation with minimal blast radius—an AI agent misusing it could only cause benign HTTP requests to arbitrary URLs, which poses negligible security risk. No data is modified, deleted, executed, or financial operations are involved.

From the tool's definition Tool description states 'Check if a URL is accessible without downloading the content' — this performs a non-destructive status check (HTTP HEAD or similar) that retrieves only metadata about accessibility, with no side effects on the target resource or the…

Questions about checkWebsiteStatus

What does the checkWebsiteStatus tool do? +

Check if a URL is accessible without downloading the content. It is categorised as a Read tool in the Advanced Web Fetching MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on checkWebsiteStatus? +

Register the Advanced Web Fetching MCP Server MCP server in PolicyLayer and add a rule for checkWebsiteStatus: 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 Advanced Web Fetching MCP Server. Nothing to install.

What risk level is checkWebsiteStatus? +

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

Can I rate-limit checkWebsiteStatus? +

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

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

checkWebsiteStatus is provided by the Advanced Web Fetching MCP Server MCP server (llmbaseai/mcp-servers). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.