High Risk →

changedetection_recheck

Trigger an immediate recheck of one watch. Returns once the request is queued (the fetch may still be running).

How to control changedetection_recheck ↓

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.

High Risk

Why changedetection_recheck needs a policy

This tool executes an external operation (website/content recheck) whose outcome depends on what is being watched and when. While not destructive and not creating persistent data modifications, it actively triggers a remote fetch operation and queues background work, which aligns with Execute category.

From the tool's definition Tool description states 'Trigger an immediate recheck of one watch' and 'returns once the request is queued (the fetch may still be running)' — indicates execution of a fetch/network operation triggered on demand with externally observable side effects.

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

How to control changedetection_recheck

PolicyLayer is an MCP gateway — it sits between your AI agents and Crow, and nothing reaches the server without passing your rules. This is the rule we recommend for changedetection_recheck:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "changedetection_recheck": {
      "limits": [
        {
          "counter": "changedetection_recheck_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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.

  1. Create a free account and register Crow — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about changedetection_recheck

What does the changedetection_recheck tool do? +

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.

How do I enforce a policy on changedetection_recheck? +

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.

What risk level is changedetection_recheck? +

changedetection_recheck is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit changedetection_recheck? +

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.

How do I block changedetection_recheck completely? +

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.

What MCP server provides changedetection_recheck? +

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.

Enforce policy on every Crow tool call.

Start from Crow, 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.

576 Crow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.