fft_transform
Fast Fourier Transform (Cooley-Tukey radix-2) with optional inverse.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/fft-transform.md
What fft_transform does on UnClick
AI agents invoke fft_transform to trigger actions in UnClick. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
signal | array | Yes | Array of real-valued samples. |
inverse | boolean | — | Perform inverse FFT (default false). |
Parameters from the server's own tool schema.
Why fft_transform is rated High
This is a mathematical computation tool that executes a Fast Fourier Transform algorithm. While it performs code execution, the blast radius is minimal—it transforms numerical data deterministically without side effects on external systems, data persistence, or financial impact. The tool is Execute rather than Read because it actively runs a computational algorithm rather than merely retrieving data.
From the tool's definition Tool performs FFT computation using Cooley-Tukey radix-2 algorithm with optional inverse transform. Performs mathematical computation that executes code on input data.
Attacks that exploit this kind of access
The rule that runs fft_transform safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fft_transform, this is the rule to start with:
fft_transform stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every fft_transform call is checked against it from then on.
Questions about fft_transform
Fast Fourier Transform (Cooley-Tukey radix-2) with optional inverse. It is categorised as a Execute tool in the UnClick MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
fft_transform accepts 2 parameters: signal, inverse. Required: signal. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for fft_transform: 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 UnClick. Nothing to install.
fft_transform is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the fft_transform 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 fft_transform. 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.
fft_transform is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
Across the catalogue