changedetection_list_changes

List recent change events across all watches. Useful for

SERVERCrow SOURCEkh0pper/crow
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/kh0pper-crow/changedetection-list-changes.md

What changedetection_list_changes does on Crow

AI agents call changedetection_list_changes to retrieve information from Crow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why changedetection_list_changes is rated Low

This tool queries and retrieves change event history without creating, modifying, deleting, or executing operations. It is a read-only operation that observes past changes to monitored resources. The blast radius of misuse is minimal—an agent could only access existing change logs, not alter system state or trigger actions.

From the tool's definition Tool name 'changedetection_list_changes' and description 'List recent change events across all watches' indicate retrieval of historical change data with no modification capability.

Questions about changedetection_list_changes

What does the changedetection_list_changes tool do? +

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.

How do I enforce a policy on changedetection_list_changes? +

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.

What risk level is changedetection_list_changes? +

changedetection_list_changes is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit changedetection_list_changes? +

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.

How do I block changedetection_list_changes completely? +

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.

What MCP server provides changedetection_list_changes? +

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.

More on Crow, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Crow's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.