Show how code files changed over time.
AI agents call get_code_changes to retrieve information from Screen Memory without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays historical code changes without modifying, deleting, or executing anything. It is a semantic search/timeline feature over captured screen memory, similar to the sibling tools get_activity_timeline and search_screen_memory. No side effects or irreversible actions are possible.
From the tool's definition Tool name 'get_code_changes' and description 'Show how code files changed over time' indicate a retrieval operation.
Attacks that exploit this kind of access
Show how code files changed over time. It is categorised as a Read tool in the Screen Memory MCP Server, which means it retrieves data without modifying state.
Register the Screen Memory MCP server in PolicyLayer and add a rule for get_code_changes: 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 Screen Memory. Nothing to install.
get_code_changes 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_changes 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_changes. 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_changes is provided by the Screen Memory MCP server (yonglim2392/screen-memory-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 →