Fetch and return the text content of a webpage.
AI agents call get_webpage_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 data from web pages with no side effects. It performs a read-only operation that queries content from an external source and returns structured information. The operation is informational and non-destructive, fitting the Read category.
From the tool's definition Tool description: 'Fetch and return the text content of a webpage.' The verb 'fetch' and 'return' indicate retrieval without modification. No creation, deletion, execution, or financial operations are mentioned.
Documented attack patterns abuse exactly the kind of access get_webpage_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_webpage_content:
{
"version": "1",
"default": "deny",
"tools": {
"get_webpage_content": {}
}
}get_webpage_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 return the text content of a webpage. 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_webpage_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_webpage_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_webpage_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_webpage_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_webpage_content is provided by the Web Search MCP server (pranavms13/web-search-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Web Search MCP, 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.
4 Web Search MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.