Get the current sync status and database statistics.
AI agents call get_sync_status to retrieve information from Fellow MCP Server 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 metadata about the sync process and database state. It is a read-only query that returns status information and statistics without any side effects, data modification, or triggering of external operations. The low severity reflects minimal blast radius if misused by an AI agent.
From the tool's definition Tool name is 'get_sync_status' and description states it 'Get[s] the current sync status and database statistics' — purely informational queries about system state with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Get the current sync status and database statistics. It is categorised as a Read tool in the Fellow MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Fellow MCP Server MCP server in PolicyLayer and add a rule for get_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 Fellow MCP Server. Nothing to install.
get_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 get_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 get_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.
get_sync_status is provided by the Fellow MCP Server MCP server (liba2k/unofficial-fellow-mcp). 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 →