get_email_pattern
Get regex pattern for email validation.
This record as markdown: /tools/io-tinyfn-tinyfn/get-email-pattern.md
What get_email_pattern does on TinyFn
AI agents call get_email_pattern 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 |
|---|---|---|---|
strict | boolean | — | Use strict RFC 5322 pattern |
Parameters from the server's own tool schema.
Why get_email_pattern is rated Low
This tool simply retrieves and returns a regex pattern string—a static, informational lookup with no capability to modify systems, execute code, or affect data. It falls cleanly into the Read category as a query/fetch operation. The blast radius of misuse is negligible since the output is a benign regex pattern.
From the tool's definition Tool name 'get_email_pattern' and description 'Get regex pattern for email validation' indicate a retrieval operation that returns a pre-built regex pattern for email validation.
Attacks that exploit this kind of access
The rule that runs get_email_pattern 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 get_email_pattern, this is the rule to start with:
get_email_pattern 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 get_email_pattern call is checked against it from then on.
Questions about get_email_pattern
Get regex pattern for email validation. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
get_email_pattern accepts 1 parameter: strict. 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 get_email_pattern: 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.
get_email_pattern 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 get_email_pattern 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 get_email_pattern. 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.
get_email_pattern 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