html_entity · Tools MCP: Risk & Policy

WHAT IT DOES

What html_entity does on Tools

AI agents use html_entity to create or update resources in Tools — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tools environment.

PARAMETERS

Parameter	Type	Required	Description
`input`	string	Yes	String to process
`action`	string	—	Action (default: auto)

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why html_entity needs a policy

An AI agent can call html_entity faster than any human can review — one bad instruction and it creates or modifies resources in Tools by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

html_entity Rate-limited

html_entity stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "html_entity": {
      "limits": [
        {
          "counter": "html_entity_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Tools, so you can run agents against it safely.

FAQ

Questions about html_entity

What does the html_entity tool do? +

Encode or decode HTML entities. It is categorised as a Write tool in the Tools MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does html_entity accept? +

html_entity accepts 2 parameters: input, action. Required: input. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on html_entity? +

Register the Tools MCP server in PolicyLayer and add a rule for html_entity: 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 Tools. Nothing to install.

What risk level is html_entity? +

html_entity is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit html_entity? +

Yes. Add a rate_limit block to the html_entity 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.

How do I block html_entity completely? +

Set action: deny in the PolicyLayer policy for html_entity. 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.

What MCP server provides html_entity? +

html_entity is provided by the Tools MCP server (https://www.jiebang.site/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.