extract_emails
Extract all email addresses from text.
This record as markdown: /tools/io-tinyfn-tinyfn/extract-emails.md
What extract_emails does on TinyFn
AI agents call extract_emails to retrieve information from TinyFn 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 to extract from |
Parameters from the server's own tool schema.
Why extract_emails is rated Low
This tool reads and analyzes input text to identify and return email addresses. It performs pattern matching and extraction without creating, modifying, deleting, or executing external operations. The operation is query-like (search/identify), producing informational output only. No destructive, financial, or code execution capabilities are present. Low severity due to minimal blast radius if misused by an agent.
From the tool's definition Tool name 'extract_emails' and description 'Extract all email addresses from text' indicate data retrieval/parsing without modification or side effects.
Attacks that exploit this kind of access
The rule that runs extract_emails safely
PolicyLayer is an MCP gateway: it sits between your AI agents and TinyFn, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For extract_emails, this is the rule to start with:
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 TinyFn, apply this rule, and every extract_emails call is checked against it from then on.
Questions about extract_emails
Extract all email addresses from text. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
extract_emails accepts 1 parameter: text. Required: text. The full parameter table on this page comes from the server's own tool schema.
Register the TinyFn MCP server in PolicyLayer and add a rule for 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 TinyFn. Nothing to install.
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 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 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.
extract_emails is provided by the TinyFn MCP server (https://api.tinyfn.io/mcp/all/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on TinyFn, and thousands of servers like it.
This server
Across the catalogue