Export all pages and links for a crawl job as structured dict.
AI agents call sicry_crawl_export to retrieve information from Sicry without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool reads and exports data from a completed crawl job as a structured dictionary. This is a read/fetch operation with no side effects. Severity is medium because it operates in a Tor/dark web context, meaning the exported data could contain sensitive or illicit content, but the tool itself only retrieves already-collected data.
From the tool's definition 'Export all pages and links for a crawl job as structured dict' — retrieves/exports existing crawl data without modifying it
Documented attack patterns abuse exactly the kind of access sicry_crawl_export gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sicry, and nothing reaches the server without passing your rules. This is the rule we recommend for sicry_crawl_export:
{
"version": "1",
"default": "deny",
"tools": {
"sicry_crawl_export": {}
}
}sicry_crawl_export 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.
Export all pages and links for a crawl job as structured dict. It is categorised as a Read tool in the Sicry MCP Server, which means it retrieves data without modifying state.
Register the Sicry MCP server in PolicyLayer and add a rule for sicry_crawl_export: 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 Sicry. Nothing to install.
sicry_crawl_export 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 sicry_crawl_export 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 sicry_crawl_export. 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.
sicry_crawl_export is provided by the Sicry MCP server (jacobjandon/sicry). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Sicry, 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.
15 Sicry tools catalogued and risk-classified — across an index of 43,000+ MCP servers.