Scrape web pages using Scrapling via OmniMesh. Modes: http (TLS-spoofed, ~200ms), browser (Playwright JS rendering), stealth (Camoufox + Cloudflare Turnstile bypass). Auto-installs on target node if missing. Routes through WireGuard mesh. Supports VPN routing (via_vpn), bulk URLs with session poo...
AI agents invoke omniwire_scrape to trigger actions in OmniWire. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes browser automation and web scraping operations on remote nodes, including JavaScript rendering via Playwright, stealth bypass of anti-bot protections (Cloudflare Turnstile), and can auto-install software on target nodes. It triggers external network operations routed through a WireGuard mesh VPN.
From the tool's definition Playwright JS rendering, Camoufox + Cloudflare Turnstile bypass, Routes through WireGuard mesh, Auto-installs on target node if missing, bulk URLs with session pooling
Documented attack patterns abuse exactly the kind of access omniwire_scrape 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_scrape:
{
"version": "1",
"default": "deny",
"tools": {
"omniwire_scrape": {
"limits": [
{
"counter": "omniwire_scrape_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} omniwire_scrape stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Scrape web pages using Scrapling via OmniMesh. Modes: http (TLS-spoofed, ~200ms), browser (Playwright JS rendering), stealth (Camoufox + Cloudflare Turnstile bypass). Auto-installs on target node if missing. Routes through WireGuard mesh. Supports VPN routing (via_vpn), bulk URLs with session pooling, CSS/XPath selectors, adaptive self-healing selectors. Actions: scrape (default), install, status. It is categorised as a Execute tool in the OmniWire MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the OmniWire MCP server in PolicyLayer and add a rule for omniwire_scrape: 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_scrape is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the omniwire_scrape 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_scrape. 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_scrape 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.