running_stats
Compute running (sliding window) mean, standard deviation, min, and max over a numeric array.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/running-stats.md
What running_stats does on UnClick
AI agents invoke running_stats 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 |
|---|---|---|---|
data | array | Yes | Numeric data array |
window | integer | — | Window size (default 5) |
Parameters from the server's own tool schema.
Why running_stats is rated High
This tool executes a statistical computation over a numeric array. It does not read from external sources, write data, or cause destructive/financial effects. It falls under Execute as it runs a calculation algorithm. Severity is low since it only processes user-supplied numbers with no external side effects or system access.
From the tool's definition 'Compute running (sliding window) mean, standard deviation, min, and max over a numeric array' — performs a calculation/computation over provided data
Attacks that exploit this kind of access
The rule that runs running_stats 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 running_stats, this is the rule to start with:
running_stats 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 running_stats call is checked against it from then on.
Questions about running_stats
Compute running (sliding window) mean, standard deviation, min, and max over a numeric array. 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.
running_stats accepts 2 parameters: data, window. Required: data. 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 running_stats: 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.
running_stats 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 running_stats 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 running_stats. 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.
running_stats 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