Feed sync status: running/stopped, last_full_sync timestamp, last_delta_sync, recent errors.
AI agents call sync_status to retrieve information from Mcp Revelor without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
sync_status queries operational state and timestamps without modifying data, triggering external operations, or creating financial obligations. It is purely informational/diagnostic, fitting the Read category. Severity is low because misuse merely returns operational metadata without blast radius. Confidence is high given the explicit status-reporting nature of the description.
From the tool's definition Tool retrieves status information: 'running/stopped', 'last_full_sync timestamp', 'last_delta_sync', 'recent errors'. These are read-only queries of system state with no side effects.
Attacks that exploit this kind of access
Feed sync status: running/stopped, last_full_sync timestamp, last_delta_sync, recent errors. It is categorised as a Read tool in the Mcp Revelor MCP Server, which means it retrieves data without modifying state.
Register the Mcp Revelor 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 Mcp Revelor. 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 Mcp Revelor MCP server (webotvurci-s-r-o/mcp-revelor). 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 →