AI agents call changes_to 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.
Despite the empty description, contextual evidence points to a read operation: the server's purpose is indexing and navigation, and the tool name suggests querying what changed relative to something (git history context). No evidence of modification, execution, deletion, or financial impact.
From the tool's definition Tool name 'changes_to' in a code indexing server ('Deep code indexing for AI agents. Search symbols, navigate call graphs...track git history'). Sibling tools include 'detect_changes', 'blame_symbol', and other query/analysis operations.
Documented attack patterns abuse exactly the kind of access changes_to 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 changes_to:
{
"version": "1",
"default": "deny",
"tools": {
"changes_to": {}
}
}changes_to 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.
changes_to. 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 changes_to: 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.
changes_to 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 changes_to 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 changes_to. 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.
changes_to 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.