List all website tools for a given website. Use this after navigating to a new site or when you expect website tools to have changed (e.g., after login, page change, or component updates)
AI agents call list_website_tools to retrieve information from WebMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only discovery operation. It queries what tools are available on a website and returns a list, similar to 'get' or 'list' operations. There are no side effects, no data modification, no code execution, and no destructive actions.
From the tool's definition Tool description states 'List all website tools for a given website' — this is a query/enumeration operation that retrieves information about available tools without modifying or executing anything.
Documented attack patterns abuse exactly the kind of access list_website_tools gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and WebMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for list_website_tools:
{
"version": "1",
"default": "deny",
"tools": {
"list_website_tools": {}
}
}list_website_tools 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.
List all website tools for a given website. Use this after navigating to a new site or when you expect website tools to have changed (e.g., after login, page change, or component updates). It is categorised as a Read tool in the WebMCP MCP Server, which means it retrieves data without modifying state.
Register the Web MCP server in PolicyLayer and add a rule for list_website_tools: 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 WebMCP. Nothing to install.
list_website_tools 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 list_website_tools 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 list_website_tools. 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.
list_website_tools is provided by the Web MCP server (miguelspizza/webmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from WebMCP, 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.
13 WebMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.