Check background sync and job queue status
AI agents call sync_status to retrieve information from r3 (Recall) without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves diagnostic information about background processes and job queues. It has no side effects and does not alter system state, making it a pure information retrieval operation. The low severity reflects that misuse poses minimal risk—an AI agent querying sync status cannot damage data or trigger unwanted operations.
From the tool's definition The description 'Check background sync and job queue status' indicates a monitoring/status inspection operation. The verb 'check' is a read operation that retrieves state information without modifying any data.
Attacks that exploit this kind of access
Check background sync and job queue status. It is categorised as a Read tool in the r3 (Recall) MCP Server, which means it retrieves data without modifying state.
Register the r3 (Recall) 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 r3 (Recall). 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 r3 (Recall) MCP server (n3wth/r3). 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 →