histogram_create
Create a histogram from numeric data with configurable bins and ASCII visualization.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/histogram-create.md
What histogram_create does on UnClick
AI agents use histogram_create to create or update resources in UnClick, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
bins | number | — | Number of bins (default 10). |
values | array | Yes | Array of numbers to histogram. |
Parameters from the server's own tool schema.
Why histogram_create is rated Medium
This tool creates a new histogram visualization object, which is a reversible write operation. It takes numeric input data and produces a formatted output (ASCII visualization), with no side effects on external systems, no code execution, and no data deletion.
From the tool's definition Tool name 'histogram_create' and description 'Create a histogram from numeric data' indicate data creation/generation. The tool generates a new histogram visualization artifact from input data.
Attacks that exploit this kind of access
The rule that runs histogram_create 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 histogram_create, this is the rule to start with:
histogram_create stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 histogram_create call is checked against it from then on.
Questions about histogram_create
Create a histogram from numeric data with configurable bins and ASCII visualization. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
histogram_create accepts 2 parameters: bins, values. Required: values. 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 histogram_create: 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.
histogram_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the histogram_create 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 histogram_create. 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.
histogram_create 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