convolution
Compute discrete convolution of a signal with a kernel. Supports full, same, and valid modes.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/convolution.md
What convolution does on UnClick
AI agents invoke convolution 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 |
|---|---|---|---|
mode | string | — | Output mode (default full) |
kernel | array | Yes | Convolution kernel array |
signal | array | Yes | Input signal array |
Parameters from the server's own tool schema.
Why convolution is rated High
This tool performs a mathematical computation (discrete convolution) on provided input data. It executes a numerical algorithm rather than simply reading stored data or writing/modifying persistent state. The blast radius is low since it only processes input values and returns a result with no side effects on external systems.
From the tool's definition Compute discrete convolution of a signal with a kernel
Attacks that exploit this kind of access
The rule that runs convolution 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 convolution, this is the rule to start with:
convolution 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 convolution call is checked against it from then on.
Questions about convolution
Compute discrete convolution of a signal with a kernel. Supports full, same, and valid modes. 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.
convolution accepts 3 parameters: mode, kernel, signal. Required: kernel, 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 convolution: 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.
convolution 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 convolution 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 convolution. 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.
convolution 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