Read one synergy file in full. Use after list_synergies to drill into a specific pattern.
AI agents call read_synergy 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 queries data from a local changelog mirror without any side effects. It is used to drill into specific patterns after listing, which is a typical read-only workflow. There is no capability to modify, delete, or execute operations. The blast radius of misuse is minimal—an agent could retrieve synergy information but cannot alter or act upon it.
From the tool's definition Tool name 'read_synergy' uses the verb 'read'. Description states 'Read one synergy file in full', explicitly indicating a retrieval operation with no modification capability.
Attacks that exploit this kind of access
Read one synergy file in full. Use after list_synergies to drill into a specific pattern. 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 read_synergy: 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.
read_synergy 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 read_synergy 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 read_synergy. 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.
read_synergy 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 →