Cumulative diff between two versions of a product, grouped by intermediate release. Use for upgrade planning (
AI agents call compare_versions 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 and compares existing version data to present differences—a read-only query operation. It has no side effects, creates no data, executes no code, and cannot delete or modify anything. The use case (upgrade planning) further confirms it is purely informational. Lowest severity due to read-only nature and limited blast radius if misused.
From the tool's definition Tool name 'compare_versions' and description 'Cumulative diff between two versions of a product' indicates retrieval and comparison of changelog data.
Attacks that exploit this kind of access
Cumulative diff between two versions of a product, grouped by intermediate release. Use for upgrade planning (. 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 compare_versions: 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.
compare_versions 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 compare_versions 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 compare_versions. 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.
compare_versions 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 →