AI agents call index_status 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.
This tool reads and reports the status of an existing code index. It has no side effects, does not modify data, and does not execute code or perform destructive operations. It is a straightforward status/state query, which falls squarely in the Read category.
From the tool's definition The tool description states 'Check the current state of the code index' — a query operation that retrieves status information without modifying or executing anything.
Documented attack patterns abuse exactly the kind of access index_status 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 index_status:
{
"version": "1",
"default": "deny",
"tools": {
"index_status": {}
}
}index_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check the current state of the code index. It is categorised as a Read tool in the Srclight MCP Server, which means it retrieves data without modifying state.
Register the Srclight MCP server in PolicyLayer and add a rule for index_status: 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.
index_status 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 index_status 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 index_status. 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.
index_status 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.
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.