List recent change events across all watches. Useful for
AI agents call changedetection_list_changes to retrieve information from Crow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists existing change detection records. It performs a query operation with no side effects, no code execution, no data modification, and no destructive actions. The blast radius of misuse is minimal—an agent could only view historical change data that has already been recorded.
From the tool's definition Tool name 'changedetection_list_changes' and description 'List recent change events across all watches' indicate a retrieval operation that queries historical change data without modifying, deleting, or executing external operations.
Documented attack patterns abuse exactly the kind of access changedetection_list_changes gives an agent:
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_list_changes:
{
"version": "1",
"default": "deny",
"tools": {
"changedetection_list_changes": {}
}
} changedetection_list_changes 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.
List recent change events across all watches. Useful for. It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.
Register the Crow MCP server in PolicyLayer and add a rule for changedetection_list_changes: 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_list_changes 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 changedetection_list_changes 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_list_changes. 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_list_changes 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.
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.