This record as markdown: /tools/io-tinyfn-tinyfn/validate-email.md
What validate_email does on TinyFn
AI agents call validate_email 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 |
|---|---|---|---|
email | string | Yes | Email address to validate |
Parameters from the server's own tool schema.
Why validate_email is rated Low
This tool retrieves and evaluates data (email format) with no side effects. It performs pattern matching or rule checking on input, returning a boolean or validation status. No data is written, deleted, or external actions triggered. Categorized as Read with low severity due to minimal blast radius if misused—worst case would be false positives/negatives in email validation logic.
From the tool's definition Tool name is 'validate_email' and description states 'Validate an email address.' Validation is a read-only operation that checks format against rules without modifying, creating, deleting, or executing anything.
Attacks that exploit this kind of access
The rule that runs validate_email 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 validate_email, this is the rule to start with:
validate_email 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 validate_email call is checked against it from then on.
Questions about validate_email
Validate an email address. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
validate_email accepts 1 parameter: email. Required: email. 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 validate_email: 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.
validate_email 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 validate_email 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 validate_email. 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.
validate_email 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