Show items that differ between local node and the sync database.
AI agents call cybersync_diff to retrieve information from OmniWire without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation—it compares state between two sources and reports differences. The verb 'Show' indicates output/retrieval with no side effects. No data is created, modified, deleted, or executed. The blast radius of misuse is minimal; an agent querying diffs cannot damage systems or data.
From the tool's definition Tool name 'cybersync_diff' and description 'Show items that differ between local node and the sync database' indicate a comparison/query operation that retrieves and displays differences without modifying any data.
Documented attack patterns abuse exactly the kind of access cybersync_diff gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OmniWire, and nothing reaches the server without passing your rules. This is the rule we recommend for cybersync_diff:
{
"version": "1",
"default": "deny",
"tools": {
"cybersync_diff": {}
}
}cybersync_diff is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Show items that differ between local node and the sync database. It is categorised as a Read tool in the OmniWire MCP Server, which means it retrieves data without modifying state.
Register the OmniWire MCP server in PolicyLayer and add a rule for cybersync_diff: 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 OmniWire. Nothing to install.
cybersync_diff 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 cybersync_diff 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 cybersync_diff. 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.
cybersync_diff is provided by the OmniWire MCP server (voidchecksum/omniwire). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OmniWire, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
88 OmniWire tools catalogued and risk-classified — across an index of 43,000+ MCP servers.