sicry_check_engines

THE RISK

Low Risk

Why sicry_check_engines needs a policy

This tool retrieves monitoring data (engine status and reliability metrics) without modifying, executing, or deleting anything. It is purely informational and read-only in nature. The low severity reflects minimal blast radius: even if an AI agent abuses this tool, it can only enumerate search engine availability on the dark web, with no destructive or financial consequences.

From the tool's definition Tool performs 'ping' and status checks on dark web search engines, returning 'status + rolling reliability score' — a query operation with no data modification, deletion, or execution of external code.

Documented attack patterns abuse exactly the kind of access sicry_check_engines gives an agent:

POLICY

How to control sicry_check_engines

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_check_engines:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sicry_check_engines": {}
  }
}

sicry_check_engines is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Sicry — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Sicry tools

Execute sicry_crawl Spider a .onion site depth-first. Extracts entities, stores in SQLite. Execute sicry_renew_identity Rotate Tor circuit — new exit node, fresh identity. Write sicry_watch_add Register a persistent watch/alert job. Re-checks every N hours, alerts on new results. Read sicry_analyze_nollm Analyse dark web content WITHOUT an LLM. Uses keyword extraction + entity regex. Works off Read sicry_ask Analyse dark web content with LLM. Returns structured OSINT report. Read sicry_check_tor Verify Tor is running. Call before any dark web operation. Read sicry_extract_keywords Extract top keywords from text using TF-IDF-like scoring. No LLM needed. Read sicry_fetch Fetch any URL through Tor (.onion or clearnet). Returns title, text, links.

All 15 Sicry tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about sicry_check_engines

What does the sicry_check_engines tool do? +

Ping 12 dark web search engines. Returns status + rolling reliability score. It is categorised as a Read tool in the Sicry MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on sicry_check_engines? +

Register the Sicry MCP server in PolicyLayer and add a rule for sicry_check_engines: 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.

What risk level is sicry_check_engines? +

sicry_check_engines is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit sicry_check_engines? +

Yes. Add a rate_limit block to the sicry_check_engines 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.

How do I block sicry_check_engines completely? +

Set action: deny in the PolicyLayer policy for sicry_check_engines. 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.

What MCP server provides sicry_check_engines? +

sicry_check_engines 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.

Enforce policy on every Sicry tool call.

Start from Sicry, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →