Manage browser cookies across mesh nodes with CyberBase persistence. Store/retrieve/import/export in json/header/netscape format and sync to remote nodes via SSH.
AI agents use cybersync_cookies to create or update resources in OmniWire — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OmniWire environment.
The tool modifies cookie state across distributed infrastructure by storing, importing, and syncing data. While it enables data retrieval (Read aspect), the core functions are create/modify operations (Write). It is not Execute (doesn't run arbitrary commands), not Destructive (cookies can be cleared/replaced), and not Financial.
From the tool's definition Tool description states 'Store/retrieve/import/export' and 'sync to remote nodes via SSH' — these are write operations that create, modify, and transfer cookie data.
Documented attack patterns abuse exactly the kind of access cybersync_cookies 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_cookies:
{
"version": "1",
"default": "deny",
"tools": {
"cybersync_cookies": {
"limits": [
{
"counter": "cybersync_cookies_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}cybersync_cookies stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Manage browser cookies across mesh nodes with CyberBase persistence. Store/retrieve/import/export in json/header/netscape format and sync to remote nodes via SSH. It is categorised as a Write tool in the OmniWire MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the OmniWire MCP server in PolicyLayer and add a rule for cybersync_cookies: 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_cookies is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the cybersync_cookies 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_cookies. 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_cookies 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.