text_keywords
utilpeek: Extract the keywords and keyphrases of a text. For raw frequencies use text_frequency; for names and places use extract_entities. Returns the top keyphrases of a text by RAKE (phrases between stop words and punctuation, scored by word degree / frequency), with score and count. Typically...
This record as markdown: /tools/dev-tanod-tanod/text-keywords.md
What text_keywords does on Tanod
AI agents call text_keywords 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). |
top_n | integer | — | Keyphrases to return, best first (1-100, default 10). |
language | string | — | Stop-word language: de, en (default), es, fr, it, nl or pt. |
max_words | integer | — | Longest keyphrase, in words. |
Parameters from the server's own tool schema.
Why text_keywords is rated Low
Even though text_keywords 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_keywords 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_keywords, this is the rule to start with:
text_keywords 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_keywords call is checked against it from then on.
Questions about text_keywords
utilpeek: Extract the keywords and keyphrases of a text. For raw frequencies use text_frequency; for names and places use extract_entities. Returns the top keyphrases of a text by RAKE (phrases between stop words and punctuation, scored by word degree / frequency), with score and count. Typically under 0.3 s. Price: USD 0.002. 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_keywords accepts 4 parameters: text, top_n, language, max_words. 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_keywords: 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_keywords 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_keywords 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_keywords. 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_keywords 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