Low Risk

text_metrics

Get text quality metrics: word count, sentence count, estimated tokens, readability grade

Part of the Ai Eval server.

text_metrics is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE AI EVAL →

Free to start. No card required.

AI agents call text_metrics to retrieve information from Ai Eval without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though text_metrics only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "text_metrics": {}
  }
}

See the full Ai Eval policy for all 3 tools.

Get this rule live on your own Ai Eval server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY AI EVAL →

These attack patterns abuse exactly the kind of access text_metrics gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so text_metrics only ever does what you allow.

SECURE AI EVAL →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the text_metrics tool do? +

Get text quality metrics: word count, sentence count, estimated tokens, readability grade. It is categorised as a Read tool in the Ai Eval MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on text_metrics? +

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

What risk level is text_metrics? +

text_metrics is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit text_metrics? +

Yes. Add a rate_limit block to the text_metrics 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 text_metrics completely? +

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

text_metrics is provided by the Ai Eval MCP server (https://api.lazy-mac.com/ai-eval/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Ai Eval tool call.

Deterministic rules across all 3 Ai Eval tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.