markov_generate
Generate text using a Markov chain trained on input text (word or character level).
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/markov-generate.md
What markov_generate does on UnClick
AI agents invoke markov_generate 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 |
|---|---|---|---|
mode | string | — | 'word' (default) or 'character'. |
text | string | Yes | Training corpus. |
order | number | — | Chain order/context size (default 2). |
length | number | — | Number of tokens to generate (default 50). |
Parameters from the server's own tool schema.
Why markov_generate is rated High
This tool runs a text generation algorithm (Markov chain training and inference) on provided input data. It executes a computational process that produces output dependent on the arguments supplied. While it doesn't modify persistent data, it performs active computation/execution rather than simple data retrieval, placing it in the Execute category.
From the tool's definition Generate text using a Markov chain trained on input text
Attacks that exploit this kind of access
The rule that runs markov_generate 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 markov_generate, this is the rule to start with:
markov_generate 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 markov_generate call is checked against it from then on.
Questions about markov_generate
Generate text using a Markov chain trained on input text (word or character level). 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.
markov_generate accepts 4 parameters: mode, text, order, length. Required: text. 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 markov_generate: 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.
markov_generate 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 markov_generate 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 markov_generate. 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.
markov_generate 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