Get sync status: total messages, unread count, agent heartbeats.
AI agents call get_status to retrieve information from Claude Sync without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries existing state (message counts, unread messages, heartbeats) and returns it without modifying, deleting, or executing anything. It matches the Read category definition: retrieves or queries data with no side effects. The blast radius of misuse is minimal—an agent could only gain visibility into coordination state, not alter it.
From the tool's definition Tool retrieves sync status including message counts and heartbeat data—a pure query operation with no side effects.
Attacks that exploit this kind of access
Get sync status: total messages, unread count, agent heartbeats. It is categorised as a Read tool in the Claude Sync MCP Server, which means it retrieves data without modifying state.
Register the Claude Sync MCP server in PolicyLayer and add a rule for get_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 Sync. Nothing to install.
get_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 get_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 get_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.
get_status is provided by the Claude Sync MCP server (the-firmament/claude-sync). 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 →