Low Risk

embedding_health

embedding_health

How to control embedding_health ↓

AI agents call embedding_health to retrieve information from Srclight without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

The name strongly implies a diagnostic query operation that retrieves health metrics about the embedding system. No description is provided, which lowers confidence slightly, but the naming pattern and context within a code indexing server indicate a read-only operation. Health checks and status queries are non-destructive information retrievals.

From the tool's definition Tool name 'embedding_health' suggests monitoring or querying the status of embeddings. The server provides 'deep code indexing' and 'embedding_status' is listed as a sibling tool, indicating this is likely a status/health check operation with no side effects.

Documented attack patterns abuse exactly the kind of access embedding_health gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Srclight, and nothing reaches the server without passing your rules. This is the rule we recommend for embedding_health:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "embedding_health": {}
  }
}

embedding_health is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Srclight — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the embedding_health tool do? +

embedding_health. It is categorised as a Read tool in the Srclight MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on embedding_health? +

Register the Srclight MCP server in PolicyLayer and add a rule for embedding_health: 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 Srclight. Nothing to install.

What risk level is embedding_health? +

embedding_health is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit embedding_health? +

Yes. Add a rate_limit block to the embedding_health 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.

How do I block embedding_health completely? +

Set action: deny in the PolicyLayer policy for embedding_health. 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.

What MCP server provides embedding_health? +

embedding_health is provided by the Srclight MCP server (srclight/srclight). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Srclight tool call.

Deterministic rules across all 42 Srclight tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

42 Srclight tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.