This record as markdown: /tools/io-tinyfn-tinyfn/is-subset.md
What is_subset does on TinyFn
AI agents call is_subset 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 | Potential subset |
array2 | string | Yes | Potential superset |
Parameters from the server's own tool schema.
Why is_subset is rated Low
This tool performs a logical comparison between two arrays to determine a subset relationship. It retrieves or evaluates a property of the input data without creating, modifying, deleting, or executing external operations. The operation is deterministic and read-only, making it a Read category tool with low severity risk.
From the tool's definition Tool name 'is_subset' and description 'Check if array1 is a subset of array2' indicate a pure query/comparison operation with no side effects or data modification.
Attacks that exploit this kind of access
The rule that runs is_subset 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 is_subset, this is the rule to start with:
is_subset 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 is_subset call is checked against it from then on.
Questions about is_subset
Check if array1 is a subset of array2. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
is_subset 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 is_subset: 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.
is_subset 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 is_subset 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 is_subset. 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.
is_subset 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