This record as markdown: /tools/io-tinyfn-tinyfn/array-interleave.md
What array_interleave does on TinyFn
AI agents call array_interleave 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 |
|---|---|---|---|
array1 | string | Yes | First comma-separated array |
array2 | string | Yes | Second comma-separated array |
Parameters from the server's own tool schema.
Why array_interleave is rated Low
This is a deterministic utility function that takes two arrays as input and produces a computed output (interleaved array). It does not create, modify, delete, or persist data; it does not execute external code or commands; it does not move funds. The operation is read-only in nature—it queries/transforms the input data without side effects.
From the tool's definition Tool name 'array_interleave' and description 'Interleave two arrays' indicate a pure data transformation operation that reads input arrays and returns a new interleaved result with no side effects, data modification, or external operations.
Attacks that exploit this kind of access
The rule that runs array_interleave 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 array_interleave, this is the rule to start with:
array_interleave 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 array_interleave call is checked against it from then on.
Questions about array_interleave
Interleave two arrays. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
array_interleave accepts 2 parameters: array1, array2. Required: array1, array2. 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 array_interleave: 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.
array_interleave 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 array_interleave 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 array_interleave. 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.
array_interleave 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