openRouter_create_embeddings
Generate vector embeddings using an AI model
This record as markdown: /tools/io-github-alifanov-scopegate/openrouter-create-embeddings.md
What openRouter_create_embeddings does on ScopeGate
AI agents invoke openRouter_create_embeddings to trigger actions in ScopeGate. 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.
Why openRouter_create_embeddings is rated High
Generating embeddings involves calling an external AI model (via OpenRouter), which constitutes executing an external operation with compute and API cost implications. It is not a simple read (no existing data is retrieved) nor a write (no persistent data is stored).
From the tool's definition 'Generate vector embeddings using an AI model' — triggers an external AI model inference operation
Attacks that exploit this kind of access
The rule that runs openRouter_create_embeddings safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScopeGate, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For openRouter_create_embeddings, this is the rule to start with:
openRouter_create_embeddings 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 ScopeGate, apply this rule, and every openRouter_create_embeddings call is checked against it from then on.
Questions about openRouter_create_embeddings
Generate vector embeddings using an AI model. It is categorised as a Execute tool in the ScopeGate MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ScopeGate MCP server in PolicyLayer and add a rule for openRouter_create_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 ScopeGate. Nothing to install.
openRouter_create_embeddings 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 openRouter_create_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 openRouter_create_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.
openRouter_create_embeddings is provided by the ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScopeGate, and thousands of servers like it.
Across the catalogue