Get all changes in a date window, grouped by product+version. The LLM-orientation tool:
AI agents call get_changes_since to retrieve information from Claude Synergy without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical changelog data within a specified date range and returns it organized by product and version. It performs no side effects, does not execute code or commands, does not create or modify data, and does not delete anything. It is purely informational, fitting squarely into the Read category. The low severity reflects the benign nature of accessing version history metadata.
From the tool's definition Tool description states 'Get all changes in a date window, grouped by product+version' - a retrieval operation with no mutation, deletion, or execution capabilities. The verb 'Get' and the context of querying a changelog mirror indicate read-only data access.
Attacks that exploit this kind of access
Get all changes in a date window, grouped by product+version. The LLM-orientation tool:. It is categorised as a Read tool in the Claude Synergy MCP Server, which means it retrieves data without modifying state.
Register the Claude Synergy MCP server in PolicyLayer and add a rule for get_changes_since: 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 Claude Synergy. Nothing to install.
get_changes_since 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_changes_since 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_changes_since. 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_changes_since is provided by the Claude Synergy MCP server (mcp-tool-shop-org/claude-synergy). 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 →