fetch_page_content
AI agents call fetch_page_content to retrieve information from Web Search MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries page content from the web with no side effects—a classic Read operation. The empty description reduces confidence slightly, but the naming and server context clearly indicate data retrieval, not modification, execution, or deletion. Severity is low because fetching public web content poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'fetch_page_content' and server context indicate retrieval of web page content. Description is empty, but sibling tool 'search_web' and server purpose (web search and content extraction) confirm read-only data retrieval.
Attacks that exploit this kind of access
fetch_page_content. It is categorised as a Read tool in the Web Search MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Web Search MCP Server MCP server in PolicyLayer and add a rule for fetch_page_content: 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 Web Search MCP Server. Nothing to install.
fetch_page_content 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 fetch_page_content 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 fetch_page_content. 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.
fetch_page_content is provided by the Web Search MCP Server MCP server (vishalkg/web-search). 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 →