cohere_generate
Generate text completions using Cohere Command models.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/cohere-generate.md
What cohere_generate does on UnClick
AI agents invoke cohere_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 |
|---|---|---|---|
model | string | — | Model ID (default: command) |
prompt | string | Yes | |
api_key | string | — | |
max_tokens | number | — | |
temperature | number | — | |
stop_sequences | string | — | JSON array of stop strings |
Parameters from the server's own tool schema.
Why cohere_generate is rated High
This tool triggers an external API call to Cohere's language models to generate text. It executes an operation against an external service whose output depends entirely on the input prompt. While it doesn't directly modify data or move money, it runs an external computation with variable effects (e.g., generating harmful content, leaking context, or producing misleading outputs), placing it in the Execute category.
From the tool's definition Generate text completions using Cohere Command models
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs cohere_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 cohere_generate, this is the rule to start with:
cohere_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 cohere_generate call is checked against it from then on.
Questions about cohere_generate
Generate text completions using Cohere Command models. 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.
cohere_generate accepts 6 parameters: model, prompt, api_key, max_tokens, temperature, stop_sequences. Required: prompt. 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 cohere_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.
cohere_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 cohere_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 cohere_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.
cohere_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