This record as markdown: /tools/io-tinyfn-tinyfn/regex-split.md
What regex_split does on TinyFn
AI agents call regex_split 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 | Text to split |
pattern | string | Yes | Regular expression pattern to split on |
max_split | integer | — | Maximum splits (0=unlimited) |
Parameters from the server's own tool schema.
Why regex_split is rated Low
This tool performs a deterministic string operation that analyzes and transforms text into multiple parts without side effects. It reads input and returns computed results (split segments), fitting the Read category for data retrieval/transformation. The low severity reflects minimal blast radius even if misused—it cannot access external systems, delete data, execute code, or cause financial impact.
From the tool's definition Tool name 'regex_split' and description 'Split text by regex pattern' indicate a text processing operation that retrieves/queries data by partitioning input text according to a pattern. No modification, deletion, or execution of external operations occurs.
Attacks that exploit this kind of access
The rule that runs regex_split 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 regex_split, this is the rule to start with:
regex_split 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 regex_split call is checked against it from then on.
Questions about regex_split
Split text by regex pattern. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
regex_split accepts 3 parameters: text, pattern, max_split. Required: text, pattern. 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 regex_split: 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.
regex_split 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 regex_split 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 regex_split. 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.
regex_split 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