text_frequency
utilpeek: Count word and n-gram frequencies in a text. For scored keyphrases use text_keywords. Returns the most frequent words or 2-3 word n-grams (n-grams never cross punctuation) with count and share, dropping stop words (en, es, fr, de, pt, it, nl, or none), and optionally character counts. T...
This record as markdown: /tools/dev-tanod-tanod/text-frequency.md
What text_frequency does on Tanod
AI agents call text_frequency 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 |
|---|---|---|---|
text | string | Yes | The text (at most 200,000 characters). |
ngram | integer | — | Term length in words: 1 (default), 2 or 3; n-grams never span punctuation. |
top_n | integer | — | Most frequent terms to return (1-1000, default 50). |
language | string | — | Stop-word list to drop (none = keep every word). |
characters | boolean | — | Also count characters (whitespace excluded). |
min_length | integer | — | Shortest word counted, in characters (1-50, default 1; single words only, ngram=1). |
case_sensitive | boolean | — | Count "Word" and "word" apart (default false: terms are lowercased). |
include_numbers | boolean | — | Also count numeric tokens such as 2026 (default false). |
remove_stopwords | boolean | — | Drop the stop words of `language` (default true). |
Parameters from the server's own tool schema.
Why text_frequency is rated Low
Even though text_frequency 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_frequency 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_frequency, this is the rule to start with:
text_frequency 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_frequency call is checked against it from then on.
Questions about text_frequency
utilpeek: Count word and n-gram frequencies in a text. For scored keyphrases use text_keywords. Returns the most frequent words or 2-3 word n-grams (n-grams never cross punctuation) with count and share, dropping stop words (en, es, fr, de, pt, it, nl, or none), and optionally character counts. Typically under 0.3 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/keyword-extraction-api.html. It is categorised as a Read tool in the Tanod MCP Server, which means it retrieves data without modifying state.
text_frequency accepts 9 parameters: text, ngram, top_n, language, characters, min_length, case_sensitive, include_numbers, remove_stopwords. 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_frequency: 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_frequency 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_frequency 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_frequency. 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_frequency 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