Strip all HTML tags from a newsletter body to return clean plain text. e.g.,
AI agents call extract_plain_text to retrieve information from Newsletter Tools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and processes existing content (HTML stripping) without creating, modifying, deleting, or executing any operations. It is a read operation that extracts and reformats data for consumption. The low severity reflects that misuse cannot damage data or trigger unintended external effects.
From the tool's definition Tool description states 'Strip all HTML tags from a newsletter body to return clean plain text' — a pure data transformation and extraction operation with no side effects, state changes, or external action triggers.
Attacks that exploit this kind of access
Strip all HTML tags from a newsletter body to return clean plain text. e.g.,. It is categorised as a Read tool in the Newsletter Tools MCP Server, which means it retrieves data without modifying state.
Register the Newsletter Tools MCP server in PolicyLayer and add a rule for extract_plain_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 Newsletter Tools. Nothing to install.
extract_plain_text 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 extract_plain_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.
Set action: deny in the PolicyLayer policy for extract_plain_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.
extract_plain_text is provided by the Newsletter Tools MCP server (josephtandle/beehiiv-mcp-mcp). 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 →