changedetection_recheck
Trigger an immediate recheck of one watch. Returns once the request is queued (the fetch may still be running).
This record as markdown: /tools/kh0pper-crow/changedetection-recheck.md
What changedetection_recheck does on Crow
AI agents invoke changedetection_recheck to trigger actions in Crow. 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.
Why changedetection_recheck is rated High
This tool triggers an external operation (a recheck/fetch) rather than simply retrieving stored data. It performs a side effect—initiating a network request or monitoring action—making it an Execute category tool.
From the tool's definition Tool 'changedetection_recheck' with description 'Trigger an immediate recheck of one watch' performs an active operation that initiates an external fetch/monitoring request, which is an execution of a defined operation whose effects depend on which watch is…
Attacks that exploit this kind of access
The rule that runs changedetection_recheck safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For changedetection_recheck, this is the rule to start with:
changedetection_recheck 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every changedetection_recheck call is checked against it from then on.
Questions about changedetection_recheck
Trigger an immediate recheck of one watch. Returns once the request is queued (the fetch may still be running). It is categorised as a Execute tool in the Crow MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Crow MCP server in PolicyLayer and add a rule for changedetection_recheck: 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 Crow. Nothing to install.
changedetection_recheck 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 changedetection_recheck 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 changedetection_recheck. 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.
changedetection_recheck is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crow, and thousands of servers like it.
This server
Across the catalogue