text_extract_emails
Extract all email addresses from a text.
This record as markdown: /tools/creativelead-unclick/text-extract-emails.md
What text_extract_emails does on UnClick
AI agents call text_extract_emails 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_emails is rated Low
This tool parses input text to identify and extract email addresses, which is a read-only operation that queries/retrieves information without creating, modifying, deleting, or executing any actions. The blast radius of misuse is minimal—an attacker could extract emails from provided text, but cannot modify systems, execute code, or cause irreversible harm.
From the tool's definition Tool name 'text_extract_emails' and description 'Extract all email addresses from a text' indicate a retrieval/parsing operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs text_extract_emails 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_emails, this is the rule to start with:
text_extract_emails 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_emails call is checked against it from then on.
Questions about text_extract_emails
Extract all email addresses 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_emails 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_emails: 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_emails 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_emails 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_emails. 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_emails 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