text_extract
utilpeek: Extract emails, URLs, domains, IPs, dates and crypto addresses from text. To mask personal data use redact_pii; for names and places use extract_entities. Returns the emails, URLs, domains (ICANN suffixes), IPv4 / IPv6, phone-like numbers, hashtags, mentions, EVM and BTC addresses (Base...
This record as markdown: /tools/dev-tanod-tanod/text-extract.md
What text_extract does on Tanod
AI agents call text_extract 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). |
types | object | — | Default: all types. |
max_per_type | integer | — | Most distinct items returned per type (1-1000, default 100); `truncated` says when more were found. |
Parameters from the server's own tool schema.
Why text_extract is rated Low
Even though text_extract 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_extract 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_extract, this is the rule to start with:
text_extract 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_extract call is checked against it from then on.
Questions about text_extract
utilpeek: Extract emails, URLs, domains, IPs, dates and crypto addresses from text. To mask personal data use redact_pii; for names and places use extract_entities. Returns the emails, URLs, domains (ICANN suffixes), IPv4 / IPv6, phone-like numbers, hashtags, mentions, EVM and BTC addresses (Base58Check / Bech32 checksums verified) and dates (normalised to ISO) found in the text, deduplicated and counted in first-seen order; patterns run on RE2 and each hit is re-checked. Phone hits are phone-like digit groups, not validated numbers (see /v1/phone). Typically under 0.7 s. Price: USD 0.001. Free: 10 utilpeek calls per IP per UTC day. The submitted text is never logged or stored. It is categorised as a Read tool in the Tanod MCP Server, which means it retrieves data without modifying state.
text_extract accepts 3 parameters: text, types, max_per_type. 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_extract: 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_extract 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_extract 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_extract. 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_extract 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