fetch_page
AI agents call fetch_page to retrieve information from openwebui-tools MCP server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'fetch_page' most naturally indicates retrieving or reading web page data without modification. Given the server's focus on information retrieval (search, stock data, transcripts, location queries) and the absence of any mutative terminology or description, this is classified as Read.
From the tool's definition Tool name 'fetch_page' suggests retrieval of web page content; contextual sibling tools include 'search_web' and 'query_wolfram_alpha' (both read-only). Description is empty, which reduces confidence.
Attacks that exploit this kind of access
fetch_page. It is categorised as a Read tool in the openwebui-tools MCP server MCP Server, which means it retrieves data without modifying state.
Register the openwebui-tools MCP server MCP server in PolicyLayer and add a rule for fetch_page: 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 openwebui-tools MCP server. Nothing to install.
fetch_page 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 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. 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 is provided by the openwebui-tools MCP server MCP server (madelponte/mcp-server). 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 →