This record as markdown: /tools/io-tinyfn-tinyfn/random-color-2.md
What random_color_2 does on TinyFn
AI agents call random_color_2 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 |
|---|---|---|---|
count | integer | — | Number of colors to generate |
format | string | — | Output format: hex, rgb, hsl, rgba |
Parameters from the server's own tool schema.
Why random_color_2 is rated Low
This tool generates random color values and returns them to the caller. It performs a read-like operation (generating data for consumption) with no ability to modify state, delete data, execute code, or affect financial systems. The lack of any input parameters that could affect external systems and the purely generative nature of the function place it squarely in the Read category with low severity risk.
From the tool's definition Tool name 'random_color_2' and description 'Generate random color(s)' indicate data retrieval/generation with no side effects, no data modification, no external operations, and no destructive or financial impact.
Attacks that exploit this kind of access
The rule that runs random_color_2 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 random_color_2, this is the rule to start with:
random_color_2 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 random_color_2 call is checked against it from then on.
Questions about random_color_2
Generate random color(s). It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
random_color_2 accepts 2 parameters: count, format. 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 random_color_2: 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.
random_color_2 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 random_color_2 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 random_color_2. 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.
random_color_2 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