AI agents call html_encode to retrieve information from TinyFn without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
text | string | Yes | Text to HTML encode |
Parameters from the server's own tool schema.
HTML encoding is a pure data transformation function with no side effects. It reads input text and returns encoded output without modifying external state, creating resources, executing code, deleting data, or moving money. This is a safe utility function typical of encoding/validation tools in a utility library.
From the tool's definition Tool name is 'html_encode' with description: 'HTML encode text (escape special characters).' This is a deterministic transformation utility that converts text by escaping special characters for safe HTML representation.
Attacks that exploit this kind of access
HTML encode text (escape special characters). It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
html_encode accepts 1 parameter: text. Required: text. The full parameter table on this page comes from the server's own tool schema.
Register the TinyFn MCP server in PolicyLayer and add a rule for html_encode: 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 TinyFn. Nothing to install.
html_encode 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_encode 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_encode. 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_encode is provided by the TinyFn MCP server (https://api.tinyfn.io/mcp/all/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
html_encode is one line of TinyFn's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →