AI agents use cohere_embed 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 |
|---|---|---|---|
model | string | — | Embed model (default: embed-english-v3.0) |
texts | string | Yes | JSON array of strings to embed |
api_key | string | — | |
input_type | string | — | search_document, search_query, classification, clustering |
Parameters from the server's own tool schema.
An AI agent can call cohere_embed faster than any human can review — one bad instruction and it creates or modifies resources in UnClick by the hundred, each call as confident as the last.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
Create vector embeddings for text using Cohere's embed models. 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.
cohere_embed accepts 4 parameters: model, texts, api_key, input_type. Required: texts. 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_embed: 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_embed 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 cohere_embed 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_embed. 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_embed 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →