text_extract_phone_numbers
Extract all phone numbers from a text.
This record as markdown: /tools/creativelead-unclick/text-extract-phone-numbers.md
What text_extract_phone_numbers does on UnClick
AI agents call text_extract_phone_numbers to retrieve information from UnClick 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 | — |
Parameters from the server's own tool schema.
Why text_extract_phone_numbers is rated Low
This tool performs text analysis to extract and return phone numbers, which is fundamentally a read operation. It has no side effects, does not modify data, execute code, delete information, or move money. The main risk is information disclosure of phone numbers from input text, but the tool itself is passive data extraction.
From the tool's definition Tool description states 'Extract all phone numbers from a text' - a retrieval operation that parses and returns data without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
The rule that runs text_extract_phone_numbers safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For text_extract_phone_numbers, this is the rule to start with:
text_extract_phone_numbers 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 UnClick, apply this rule, and every text_extract_phone_numbers call is checked against it from then on.
Questions about text_extract_phone_numbers
Extract all phone numbers from a text. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
text_extract_phone_numbers accepts 1 parameter: text. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for text_extract_phone_numbers: 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 UnClick. Nothing to install.
text_extract_phone_numbers 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_phone_numbers 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_phone_numbers. 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_phone_numbers is provided by the UnClick MCP server (creativelead/unclick). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue