Cookie management across mesh nodes. Import/export/convert between JSON, Header string, and Netscape cookies.txt formats. Sync cookies between nodes. Extract from Chrome/Firefox.
AI agents call omniwire_cookies 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.
While cookies are sensitive authentication/session tokens that could be misused for authentication bypass or session hijacking if extracted without authorization, the tool itself is fundamentally a Read operation—it retrieves, exports, and converts cookie data.
From the tool's definition Tool handles cookie management including 'Import/export/convert between JSON, Header string, and Netscape cookies.txt formats' and 'Extract from Chrome/Firefox'. Primarily retrieves and transforms cookie data without modifying backend systems.
Documented attack patterns abuse exactly the kind of access omniwire_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 omniwire_cookies:
{
"version": "1",
"default": "deny",
"tools": {
"omniwire_cookies": {}
}
}omniwire_cookies 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.
Cookie management across mesh nodes. Import/export/convert between JSON, Header string, and Netscape cookies.txt formats. Sync cookies between nodes. Extract from Chrome/Firefox. 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 omniwire_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.
omniwire_cookies 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 omniwire_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 omniwire_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.
omniwire_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.