AI agents call get_page_content to retrieve information from Web Search MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and extracts publicly available web content without creating, modifying, deleting, or executing any operations. It has a minimal blast radius—worst case is exposure of already-public information or unauthorized access to paywalled content, neither of which causes irreversible harm or resource compromise.
From the tool's definition Tool name 'get_page_content' and description 'Fetch and extract content from a specific URL' indicate data retrieval with no modification.
Documented attack patterns abuse exactly the kind of access get_page_content gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Web Search MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_page_content:
{
"version": "1",
"default": "deny",
"tools": {
"get_page_content": {}
}
}get_page_content 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.
Fetch and extract content from a specific URL. It is categorised as a Read tool in the Web Search MCP MCP Server, which means it retrieves data without modifying state.
Register the Web Search MCP server in PolicyLayer and add a rule for get_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. Nothing to install.
get_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 get_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 get_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.
get_page_content is provided by the Web Search MCP server (uk0/web-search-fast). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 3 Web Search MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
3 Web Search MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.