embed_texts
mlpeek: Create text embeddings. For images too use embed_multimodal; for pair scores use text_similarity. Returns 384-dimension embeddings of 1-64 texts with bge-small-en-v1.5 (English) or multilingual-e5-small (about 100 languages), normalised by default; input_type applies the model's query or ...
This record as markdown: /tools/dev-tanod-tanod/embed-texts.md
What embed_texts does on Tanod
AI agents use embed_texts to create or update resources in Tanod, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tanod environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
model | string | — | small-en = BAAI/bge-small-en-v1.5 (English); multilingual = intfloat/multilingual-e5-small (~100 languages). 384 dimensions both. |
texts | array | Yes | 1-64 texts, each at most 8,000 characters; each is truncated at 512 tokens (reported per text). Priced per text, minimum USD 0.001 per call. |
encoding | string | — | base64 = little-endian float32 bytes. |
normalize | boolean | — | L2-normalise (cosine similarity = dot product). |
input_type | string | — | Retrieval prefix: query / passage (e5: 'query: ' / 'passage: '; bge: its query instruction / nothing). none = symmetric use. |
Parameters from the server's own tool schema.
Why embed_texts is rated Medium
An AI agent can call embed_texts faster than any human can review: one bad instruction and it creates or modifies resources in Tanod by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs embed_texts safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tanod, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For embed_texts, this is the rule to start with:
embed_texts stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Tanod, apply this rule, and every embed_texts call is checked against it from then on.
Questions about embed_texts
mlpeek: Create text embeddings. For images too use embed_multimodal; for pair scores use text_similarity. Returns 384-dimension embeddings of 1-64 texts with bge-small-en-v1.5 (English) or multilingual-e5-small (about 100 languages), normalised by default; input_type applies the model's query or passage prefix. Each text is cut at the model's 512-token window (truncated says so); over 16,384 tokens per request is a 422 too_many_tokens (not charged). Runs an open model pinned by hash on Tanod's own CPU (no LLM, no third-party API); an unavailable model is a 503 (not charged). Typically 20 ms for one short text, up to about 10 s at the token budget. Price: USD 0.0005 per text, at least USD 0.001 per call (1-64 texts per call: USD 0.001-0.032). Free: 5 mlpeek calls per IP per UTC day. The submitted text is never logged or stored. Docs: https://tanod.dev/learn/text-embeddings-api-no-account.html. It is categorised as a Write tool in the Tanod MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
embed_texts accepts 5 parameters: model, texts, encoding, normalize, input_type. Required: texts. The full parameter table on this page comes from the server's own tool schema.
Register the Tanod MCP server in PolicyLayer and add a rule for embed_texts: 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 Tanod. Nothing to install.
embed_texts 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 embed_texts 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 embed_texts. 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.
embed_texts is provided by the Tanod MCP server (https://tanod.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tanod, and thousands of servers like it.
This server
Across the catalogue