This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/ackermann.md
What ackermann does on UnClick
AI agents invoke ackermann 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 |
|---|---|---|---|
m | number | Yes | Non-negative integer m (max 4) |
n | number | Yes | Non-negative integer n |
Parameters from the server's own tool schema.
Why ackermann is rated High
The tool runs a computation (the Ackermann function), which can be extremely resource-intensive for large inputs due to its hyper-exponential growth. It has no side effects on data, but executing it with large m/n values could cause denial-of-service or resource exhaustion, making it Execute rather than Read. Severity is low-medium since it only computes a value but could be misused to consume resources.
From the tool's definition 'Compute the Ackermann function A(m, n)' — executes a mathematical computation
Attacks that exploit this kind of access
The rule that runs ackermann 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 ackermann, this is the rule to start with:
ackermann 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 ackermann call is checked against it from then on.
Questions about ackermann
Compute the Ackermann function A(m, n). 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.
ackermann accepts 2 parameters: m, n. Required: m, n. 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 ackermann: 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.
ackermann 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 ackermann 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 ackermann. 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.
ackermann 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