AI agents call get_code_history to retrieve information from CodeSavant without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves historical metadata about code changes. It does not execute code, modify files, delete data, or commit financial transactions. It is a read-only operation that provides visibility into version control history, presenting no risk of unintended side effects.
From the tool's definition Tool name is 'get_code_history' and description states 'Get change history for a code file' — a retrieval operation with no modification or execution.
Documented attack patterns abuse exactly the kind of access get_code_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CodeSavant, and nothing reaches the server without passing your rules. This is the rule we recommend for get_code_history:
{
"version": "1",
"default": "deny",
"tools": {
"get_code_history": {}
}
}get_code_history 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 change history for a code file. It is categorised as a Read tool in the CodeSavant MCP Server, which means it retrieves data without modifying state.
Register the CodeSavant MCP server in PolicyLayer and add a rule for get_code_history: 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 CodeSavant. Nothing to install.
get_code_history 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_code_history 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_code_history. 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_code_history is provided by the CodeSavant MCP server (twolven/mcp-codesavant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from CodeSavant, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 CodeSavant tools catalogued and risk-classified — across an index of 43,000+ MCP servers.