split_complementary_colors
Get split-complementary colors.
This record as markdown: /tools/io-tinyfn-tinyfn/split-complementary-colors.md
What split_complementary_colors does on TinyFn
AI agents call split_complementary_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 |
|---|---|---|---|
hex_color | string | Yes | Hex color |
Parameters from the server's own tool schema.
Why split_complementary_colors is rated Low
This is a deterministic utility function that queries and returns color information (split-complementary color schemes). It performs a read-only calculation/lookup with no ability to modify state, execute code, or trigger external operations. Consistent with the server's stated purpose of providing 500+ deterministic tools for math, conversion, validation, and similar operations.
From the tool's definition Tool name 'split_complementary_colors' and description 'Get split-complementary colors' indicate a retrieval operation that returns color data based on input, with no data modification, deletion, or side effects.
Attacks that exploit this kind of access
The rule that runs split_complementary_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 split_complementary_colors, this is the rule to start with:
split_complementary_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 split_complementary_colors call is checked against it from then on.
Questions about split_complementary_colors
Get split-complementary colors. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
split_complementary_colors accepts 1 parameter: 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 split_complementary_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.
split_complementary_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 split_complementary_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 split_complementary_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.
split_complementary_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