generate_shades
Generate shades (darker variations) of a color.
This record as markdown: /tools/io-tinyfn-tinyfn/generate-shades.md
What generate_shades does on TinyFn
AI agents call generate_shades 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 shades |
hex_color | string | Yes | Base hex color |
Parameters from the server's own tool schema.
Why generate_shades is rated Low
This tool performs a read/compute operation, generating darker color variations from an input color. It is purely deterministic with no data modification, execution, or financial implications. Misuse has negligible impact.
From the tool's definition Generate shades (darker variations) of a color — pure deterministic computation with no side effects
Attacks that exploit this kind of access
The rule that runs generate_shades 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 generate_shades, this is the rule to start with:
generate_shades 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 generate_shades call is checked against it from then on.
Questions about generate_shades
Generate shades (darker variations) of a color. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
generate_shades accepts 2 parameters: count, hex_color. Required: hex_color. 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 generate_shades: 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.
generate_shades 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 generate_shades 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 generate_shades. 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.
generate_shades 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