This record as markdown: /tools/io-tinyfn-tinyfn/blend-colors.md
What blend_colors does on TinyFn
AI agents call blend_colors 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 |
|---|---|---|---|
color1 | string | Yes | First hex color |
color2 | string | Yes | Second hex color |
weight | number | — | Blend weight (0-1, 0.5 = equal mix) |
Parameters from the server's own tool schema.
Why blend_colors is rated Low
This is a deterministic mathematical/algorithmic tool that performs color blending—a stateless computation. It takes color parameters as input and produces a color output without modifying any state, triggering external systems, or affecting data durability. It belongs in the Read category as it performs a calculation with no side effects.
From the tool's definition Tool name 'blend_colors' and description 'Blend two colors together' indicate a pure computation that reads color values as input and returns a blended color result with no side effects, data persistence, external operations, or destructive capabilities.
Attacks that exploit this kind of access
The rule that runs blend_colors 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 blend_colors, this is the rule to start with:
blend_colors 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 blend_colors call is checked against it from then on.
Questions about blend_colors
Blend two colors together. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
blend_colors accepts 3 parameters: color1, color2, weight. Required: color1, color2. 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 blend_colors: 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.
blend_colors 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 blend_colors 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 blend_colors. 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.
blend_colors 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