Register a persistent watch/alert job. Re-checks every N hours, alerts on new results.
AI agents use sicry_watch_add to create or update resources in Sicry — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sicry environment.
This tool creates a persistent monitoring job (write/create operation) that repeatedly re-checks Tor hidden services on a schedule. It's a Write operation because it registers a new persistent entity. Severity is high because it enables ongoing automated surveillance of dark web resources, which could be misused for persistent monitoring of illicit content or tracking sensitive targets over Tor.
From the tool's definition Register a persistent watch/alert job. Re-checks every N hours, alerts on new results.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access sicry_watch_add 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_add:
{
"version": "1",
"default": "deny",
"tools": {
"sicry_watch_add": {
"limits": [
{
"counter": "sicry_watch_add_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}sicry_watch_add stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Register a persistent watch/alert job. Re-checks every N hours, alerts on new results. It is categorised as a Write tool in the Sicry MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sicry MCP server in PolicyLayer and add a rule for sicry_watch_add: 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_add is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the sicry_watch_add 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_add. 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_add 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.