AI agents call web.read to retrieve information from TOOL4LM without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and parses HTML content to extract readable text. It has no capability to modify, delete, or execute code. The extracted content is presented to the user without side effects. This is a straightforward Read operation with minimal security risk, appropriate for an information retrieval-focused server.
From the tool's definition Tool name 'web.read' combined with description 'Extract readable content from given HTML' indicates data retrieval without modification. The verb 'extract' and the passive nature of content reading confirm read-only operations.
Attacks that exploit this kind of access
Extract readable content from given HTML (or pass html from web.fetch). It is categorised as a Read tool in the TOOL4LM MCP Server, which means it retrieves data without modifying state.
Register the TOOL4LM MCP server in PolicyLayer and add a rule for web.read: 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 TOOL4LM. Nothing to install.
web.read 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 web.read 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 web.read. 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.
web.read is provided by the TOOL4LM MCP server (khanhs-234/tool4lm). 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 →