Low Risk

get_site_info

Get information about a website without downloading it.

How to control get_site_info ↓

What get_site_info does on WebClone MCP Server

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

Low Risk

Why get_site_info needs a policy

This tool retrieves or queries website information (metadata, structure, properties) without modifying data, downloading content, or triggering external operations. It is a passive reconnaissance action with no blast radius for misuse. The absence of action verbs like 'delete', 'execute', 'create', or 'modify' confirms Read category.

From the tool's definition Tool name 'get_site_info' and description 'Get information about a website without downloading it' indicate retrieval of site metadata with no side effects or data modifications.

Documented attack patterns abuse exactly the kind of access get_site_info gives an agent:

How to control get_site_info

PolicyLayer is an MCP gateway — it sits between your AI agents and WebClone MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_site_info:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_site_info": {}
  }
}

get_site_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register WebClone MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_site_info

What does the get_site_info tool do? +

Get information about a website without downloading it. It is categorised as a Read tool in the WebClone MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_site_info? +

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

What risk level is get_site_info? +

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

Can I rate-limit get_site_info? +

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

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

get_site_info is provided by the WebClone MCP Server MCP server (ruslanmv/webclone). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every WebClone MCP Server tool call.

Start from WebClone 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.

5 WebClone MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.