Per-product sync freshness. Returns one row per product with last-fetched timestamp, hours since last fetch, and ingested release count. Use BEFORE trusting latest_releases / search results to know if the corpus is stale, and BEFORE calling sync_now to know what needs refreshing.
AI agents call sync_status 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 reports on the state of a changelog database without modifying data, executing code, or triggering external operations. It is purely informational, helping agents decide whether to trust other query results or refresh data. The blast radius of misuse is minimal—worst case, stale information guides downstream decisions, but the tool itself causes no irreversible changes or side effects.
From the tool's definition Tool returns metadata about sync status: "last-fetched timestamp, hours since last fetch, and ingested release count." It explicitly performs a query operation to check freshness, with no modification or execution implied.
Attacks that exploit this kind of access
Per-product sync freshness. Returns one row per product with last-fetched timestamp, hours since last fetch, and ingested release count. Use BEFORE trusting latest_releases / search results to know if the corpus is stale, and BEFORE calling sync_now to know what needs refreshing. 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 sync_status: 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.
sync_status 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 sync_status 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 sync_status. 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.
sync_status 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 →