Return the audit log of applied changes (most recent last).
AI agents call get_change_history to retrieve information from Safe Migrations without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries historical data about previously applied changes. It has no side effects, cannot modify state, and performs a straightforward read-only operation. The retrieval of audit logs is essential for compliance and transparency but poses minimal security risk beyond potential information disclosure (which is typically acceptable for internal audit records).
From the tool's definition Tool name is 'get_change_history' and description states it returns an 'audit log of applied changes' — a pure retrieval operation with no modification capability.
Attacks that exploit this kind of access
Return the audit log of applied changes (most recent last). It is categorised as a Read tool in the Safe Migrations MCP Server, which means it retrieves data without modifying state.
Register the Safe Migrations MCP server in PolicyLayer and add a rule for get_change_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 Safe Migrations. Nothing to install.
get_change_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_change_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_change_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_change_history is provided by the Safe Migrations MCP server (possibly6/safe-migrations-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →