game_of_life_step
Run Conway's Game of Life simulation steps (local, no network).
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/game-of-life-step.md
What game_of_life_step does on UnClick
AI agents invoke game_of_life_step 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 |
|---|---|---|---|
grid | string | — | Grid string with rows separated by newlines. '#' or '1' = alive, '.' or '0' = dead. |
steps | number | — | Number of simulation steps (default 1, max 20). |
width | number | — | Grid width for random generation (default 10, max 50). |
height | number | — | Grid height for random generation (default 10, max 50). |
Parameters from the server's own tool schema.
Why game_of_life_step is rated High
The tool executes a deterministic simulation algorithm (Conway's Game of Life) that transforms state according to defined rules. While local and mathematically deterministic with no external side effects or network access, it falls under Execute because it runs code/computation.
From the tool's definition Tool performs 'Run Conway's Game of Life simulation steps', which executes computational logic to generate outputs based on algorithm state.
Attacks that exploit this kind of access
The rule that runs game_of_life_step 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 game_of_life_step, this is the rule to start with:
game_of_life_step 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 game_of_life_step call is checked against it from then on.
Questions about game_of_life_step
Run Conway's Game of Life simulation steps (local, no network). 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.
game_of_life_step accepts 4 parameters: grid, steps, width, height. 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 game_of_life_step: 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.
game_of_life_step 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 game_of_life_step 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 game_of_life_step. 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.
game_of_life_step 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