sigmoid_calculate
Compute activation functions (sigmoid, tanh, relu, leaky_relu, elu, swish) and their derivatives.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/sigmoid-calculate.md
What sigmoid_calculate does on UnClick
AI agents invoke sigmoid_calculate 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 |
|---|---|---|---|
x | number | Yes | Input value. |
function | string | — | Activation function: sigmoid, tanh, relu, leaky_relu, elu, or swish. Default: sigmoid. |
Parameters from the server's own tool schema.
Why sigmoid_calculate is rated High
This tool performs mathematical computation/execution of activation functions. It runs calculations rather than simply retrieving stored data or modifying persistent state. Severity is low because it only computes mathematical values with no side effects on external systems or data stores.
From the tool's definition 'Compute activation functions (sigmoid, tanh, relu, leaky_relu, elu, swish) and their derivatives'
Attacks that exploit this kind of access
The rule that runs sigmoid_calculate 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 sigmoid_calculate, this is the rule to start with:
sigmoid_calculate 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 sigmoid_calculate call is checked against it from then on.
Questions about sigmoid_calculate
Compute activation functions (sigmoid, tanh, relu, leaky_relu, elu, swish) and their derivatives. 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.
sigmoid_calculate accepts 2 parameters: x, function. Required: x. 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 sigmoid_calculate: 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.
sigmoid_calculate 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 sigmoid_calculate 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 sigmoid_calculate. 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.
sigmoid_calculate 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