AI agents call get_impact 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.
The tool name 'get_impact' strongly suggests retrieval of impact analysis information (e.g., which code sections are affected by a change), with no indication of modification, deletion, or execution. The description is empty, which slightly lowers confidence, but the server context (code indexing/navigation) and naming conventions of sibling tools consistently point to a read-only operation.
From the tool's definition Tool name 'get_impact' on a code indexing server (srclight) suggests it retrieves or queries impact analysis data.
Documented attack patterns abuse exactly the kind of access get_impact 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 get_impact:
{
"version": "1",
"default": "deny",
"tools": {
"get_impact": {}
}
}get_impact 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.
get_impact. 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 get_impact: 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.
get_impact 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 get_impact 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 get_impact. 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.
get_impact 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.