Low Risk

fetch_webpage_text

fetch_webpage_text

How to control fetch_webpage_text ↓

What fetch_webpage_text does on Allcanuse

AI agents call fetch_webpage_text to retrieve information from Allcanuse without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why fetch_webpage_text needs a policy

Despite an empty description, the tool name strongly suggests a read-only operation that retrieves and returns webpage text content. This is a classic Read operation (fetch, no side effects). Low severity because webpage text retrieval poses minimal risk even if misused by an agent—it cannot modify systems, execute code, or cause financial harm.

From the tool's definition Tool name 'fetch_webpage_text' indicates retrieval of webpage content with no modification or execution capability. The 'fetch' verb and 'text' object are consistent with data retrieval operations.

Documented attack patterns abuse exactly the kind of access fetch_webpage_text gives an agent:

How to control fetch_webpage_text

PolicyLayer is an MCP gateway — it sits between your AI agents and Allcanuse, and nothing reaches the server without passing your rules. This is the rule we recommend for fetch_webpage_text:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "fetch_webpage_text": {}
  }
}

fetch_webpage_text is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Allcanuse — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about fetch_webpage_text

What does the fetch_webpage_text tool do? +

fetch_webpage_text. It is categorised as a Read tool in the Allcanuse MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on fetch_webpage_text? +

Register the Allcanuse MCP server in PolicyLayer and add a rule for fetch_webpage_text: 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 Allcanuse. Nothing to install.

What risk level is fetch_webpage_text? +

fetch_webpage_text is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit fetch_webpage_text? +

Yes. Add a rate_limit block to the fetch_webpage_text 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.

How do I block fetch_webpage_text completely? +

Set action: deny in the PolicyLayer policy for fetch_webpage_text. 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.

What MCP server provides fetch_webpage_text? +

fetch_webpage_text is provided by the Allcanuse MCP server (ra1nyxin/allcanuse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Allcanuse tool call.

Start from Allcanuse, 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.

130 Allcanuse tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.