// SCAN REPORT

HumanizeMCP

6 tools. 2 can modify or destroy data without limits.

2 write tools that can modify data. Rate limits recommended.

Last updated: 30 Jun 2026

2 can modify or destroy data

4 read-only

6 tools total

Community server · catalogue entry verified 30/06/2026

How to control HumanizeMCP ↓

TOOL MAP

What HumanizeMCP exposes to your agents

Read (4) Write / Execute (2) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous HumanizeMCP tools

Write · Medium apply_style The tool appears to apply transformations to text content, creating modified output. Write · Medium humanize Based on the server description, 'humanize' almost certainly rewrites or transforms input text, which is a Write/modify operation.

2 of HumanizeMCP's 6 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control HumanizeMCP

PolicyLayer is an MCP gateway — it sits between your AI agents and HumanizeMCP, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "apply_style": {
    "limits": [
      {
        "counter": "apply_style_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "detect_tells": {
    "limits": [
      {
        "counter": "detect_tells_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register HumanizeMCP — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON HUMANIZEMCP →

Instant setup, no code required.

FULL CATALOGUE

All 6 HumanizeMCP tools

WRITE 2 tools

Write apply_style apply_style Write humanize humanize

READ 4 tools

Read detect_tells detect_tells Read humanize_and_verify humanize_and_verify Read list_styles list_styles Read score_humanity score_humanity

FAQ

Questions about HumanizeMCP

How do I prevent bulk modifications through HumanizeMCP? +

The HumanizeMCP server has 2 write tools including apply_style, humanize. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach HumanizeMCP.

How many tools does the Humanize MCP server expose? +

6 tools across 2 categories: Read, Write. 4 are read-only. 2 can modify, create, or delete data.

How do I enforce a policy on HumanizeMCP? +

Register the Humanize MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every HumanizeMCP tool call.

Deterministic rules across all 6 HumanizeMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON HUMANIZEMCP →

Instant setup, no code required.

6 HumanizeMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// WHERE THIS COMES FROM

These policies come from Humanize's registry record.

The record behind this page: 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 →