Decode HTML-encoded input data
AI agents call decodeHtml to retrieve information from Mcp Helper Tools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a pure data transformation (HTML decoding) with no side effects, no external calls, and no data persistence. It reads input and returns a transformed output, making it a Read/utility operation with minimal blast radius.
From the tool's definition Decode HTML-encoded input data
Attacks that exploit this kind of access
Decode HTML-encoded input data. It is categorised as a Read tool in the Mcp Helper Tools MCP Server, which means it retrieves data without modifying state.
Register the Mcp Helper Tools MCP server in PolicyLayer and add a rule for decodeHtml: 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 Mcp Helper Tools. Nothing to install.
decodeHtml 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 decodeHtml 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 decodeHtml. 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.
decodeHtml is provided by the Mcp Helper Tools MCP server (missionsquad/mcp-helper-tools). 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 →