descriptive_stats
Compute descriptive statistics: mean, median, mode, std, variance, skewness, kurtosis, quartiles, IQR, and more.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/descriptive-stats.md
What descriptive_stats does on UnClick
AI agents call descriptive_stats to retrieve information from UnClick 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 |
|---|---|---|---|
data | array | Yes | Numeric data array |
Parameters from the server's own tool schema.
Why descriptive_stats is rated Low
This tool only performs statistical calculations on provided data. It retrieves and transforms data into summaries (mean, median, etc.) but does not create, modify, delete, or execute code. The operation is read-only and has no side effects beyond returning computed metrics. It poses minimal security risk as misuse would only result in incorrect statistical calculations.
From the tool's definition The tool description specifies it "Compute[s] descriptive statistics: mean, median, mode, std, variance, skewness, kurtosis, quartiles, IQR, and more." These are all passive analytical operations on data with no modification, deletion, execution, or financial…
Attacks that exploit this kind of access
The rule that runs descriptive_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 descriptive_stats, this is the rule to start with:
descriptive_stats 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 UnClick, apply this rule, and every descriptive_stats call is checked against it from then on.
Questions about descriptive_stats
Compute descriptive statistics: mean, median, mode, std, variance, skewness, kurtosis, quartiles, IQR, and more. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
descriptive_stats accepts 1 parameter: data. 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 descriptive_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.
descriptive_stats 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 descriptive_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 descriptive_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.
descriptive_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.
This server
Across the catalogue