Check all due watch jobs now. Returns new/changed result alerts.
AI agents call sicry_watch_check 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 queries the status of watch jobs and returns alerts about new or changed results. This is fundamentally a retrieval operation (Read category). However, severity is elevated to 'medium' rather than 'low' because: (1) it operates over Tor/dark web infrastructure where watch jobs may monitor sensitive or illegal content; (2) an agent could exploit alert data to identify targets or coordinate illicit…
From the tool's definition Tool name includes 'check' and description states 'Check all due watch jobs now. Returns new/changed result alerts.' – indicating it retrieves and reports status/alert data without modifying or deleting anything.
Documented attack patterns abuse exactly the kind of access sicry_watch_check 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_watch_check:
{
"version": "1",
"default": "deny",
"tools": {
"sicry_watch_check": {}
}
}sicry_watch_check 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.
Check all due watch jobs now. Returns new/changed result alerts. 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_watch_check: 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_watch_check 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_watch_check 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_watch_check. 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_watch_check 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.