Generate text embeddings via the Perplexity Embeddings API. Returns a compact summary (model, vector count, token usage) by default; pass full:true to include the raw base64-encoded vectors.
AI agents call embeddings to retrieve information from Perplexity MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Embeddings generation is a read-only operation that transforms input text into vector representations. It has no side effects on data, does not execute arbitrary code, does not modify or delete anything, and does not involve financial transactions. The tool retrieves/generates embedding vectors based on provided text—a pure read/compute operation.
From the tool's definition Tool description states it 'Generate[s] text embeddings via the Perplexity Embeddings API' and 'Returns a compact summary (model, vector count, token usage)'.
Attacks that exploit this kind of access
Generate text embeddings via the Perplexity Embeddings API. Returns a compact summary (model, vector count, token usage) by default; pass full:true to include the raw base64-encoded vectors. It is categorised as a Read tool in the Perplexity MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Perplexity MCP Server MCP server in PolicyLayer and add a rule for embeddings: 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 Perplexity MCP Server. Nothing to install.
embeddings is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the embeddings 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 embeddings. 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.
embeddings is provided by the Perplexity MCP Server MCP server (rossh121/perplexity-mcp). 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 →