text_stats
utilpeek: Count words and score the readability of a text. For word frequencies use text_frequency. Returns counts (characters, letters, words, unique words, sentences, paragraphs, averages), reading and speaking time, and for English the Flesch reading ease, Flesch-Kincaid grade, Gunning fog, SM...
This record as markdown: /tools/dev-tanod-tanod/text-stats.md
What text_stats does on Tanod
AI agents call text_stats to retrieve information from Tanod without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
lang | object | — | ISO 639 code; readability scores are computed for English only (default en); any other language gets counts only. |
text | string | Yes | The text (at most 200,000 characters). |
Parameters from the server's own tool schema.
Why text_stats is rated Low
Even though text_stats only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs text_stats safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tanod, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For text_stats, this is the rule to start with:
text_stats is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Tanod, apply this rule, and every text_stats call is checked against it from then on.
Questions about text_stats
utilpeek: Count words and score the readability of a text. For word frequencies use text_frequency. Returns counts (characters, letters, words, unique words, sentences, paragraphs, averages), reading and speaking time, and for English the Flesch reading ease, Flesch-Kincaid grade, Gunning fog, SMOG, Coleman-Liau and ARI scores (estimates from heuristic syllable counts; Dale-Chall is not offered). An unsupported lang is a 422 invalid_lang and text without words a 422 no_words (not charged). Word counts undercount scripts written without spaces. Typically under 0.2 s. Price: USD 0.001. Free: 10 utilpeek calls per IP per UTC day. The submitted text is never logged or stored. Docs: https://tanod.dev/learn/text-statistics-api.html. It is categorised as a Read tool in the Tanod MCP Server, which means it retrieves data without modifying state.
text_stats accepts 2 parameters: lang, text. Required: text. The full parameter table on this page comes from the server's own tool schema.
Register the Tanod MCP server in PolicyLayer and add a rule for text_stats: 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 Tanod. Nothing to install.
text_stats 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 text_stats 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 text_stats. 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.
text_stats is provided by the Tanod MCP server (https://tanod.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tanod, and thousands of servers like it.
This server
Across the catalogue