AI agents invoke create_embedding to trigger actions in Litellm. 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.
This tool executes an external operation (calling LiteLLM/underlying LLM provider APIs) to generate vector embeddings. It is not a simple read of stored data, nor does it write persistent data or cause destruction. It falls under Execute because it triggers external computation/API operations whose cost and effects depend on the input arguments (e.g., model chosen, input size).
From the tool's definition "Generate embeddings using LiteLLM" — triggers an external API call to a language model provider to compute embeddings
Attacks that exploit this kind of access
Generate embeddings using LiteLLM. It is categorised as a Execute tool in the Litellm MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Litellm MCP server in PolicyLayer and add a rule for create_embedding: 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 Litellm. Nothing to install.
create_embedding 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 create_embedding 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 create_embedding. 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.
create_embedding is provided by the Litellm MCP server (litellm-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 →