html_strip
Strip HTML tags and decode entities to plain text.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/html-strip.md
What html_strip does on UnClick
AI agents call html_strip to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
html | string | Yes | HTML text to strip. |
preserve_line_breaks | boolean | — | Keep line breaks from block elements (default true). |
Parameters from the server's own tool schema.
Why html_strip is rated Low
This tool performs a read-only transformation on provided text input. It parses HTML/encoded content and returns cleaned plaintext. There is no creation, modification, deletion of persistent data, no code execution, no financial impact, and no destructive capability. The operation is deterministic and reversible (the original HTML can be reconstructed from context).
From the tool's definition Tool description states it 'Strip[s] HTML tags and decode entities to plain text' — a text transformation operation with no data modification, deletion, or external side effects.
Risk signalsAccepts raw HTML/template content (html)
Attacks that exploit this kind of access
The rule that runs html_strip safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For html_strip, this is the rule to start with:
html_strip is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every html_strip call is checked against it from then on.
Questions about html_strip
Strip HTML tags and decode entities to plain text. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
html_strip accepts 2 parameters: html, preserve_line_breaks. Required: html. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for html_strip: 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 UnClick. Nothing to install.
html_strip 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 html_strip 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 html_strip. 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.
html_strip is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue