This record as markdown: /tools/io-tinyfn-tinyfn/array-zip.md
What array_zip does on TinyFn
AI agents call array_zip 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_zip is rated Low
This is a pure computational function that takes two arrays as input and returns a zipped result. It does not create, modify, delete, or execute any external operations. The function is deterministic (as stated in the server description) and belongs in the Read category as it retrieves/transforms data without persistence or side effects. Low severity due to complete absence of blast radius in misuse.
From the tool's definition Tool name 'array_zip' and description 'Zip two arrays together' indicate a deterministic array operation that combines two input arrays without modifying their original state or producing side effects.
Attacks that exploit this kind of access
The rule that runs array_zip 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_zip, this is the rule to start with:
array_zip 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_zip call is checked against it from then on.
Questions about array_zip
Zip two arrays together. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
array_zip 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_zip: 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_zip 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_zip 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_zip. 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_zip 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