watch_directory

watch_directory

Server Filesystem Watcher MCP trycatchkamal/filesystemwatcher-mcp
Category Read
Risk class Low
Parameters 00 required

What watch_directory does on Filesystem Watcher MCP

AI agents call watch_directory to retrieve information from Filesystem Watcher MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why watch_directory needs a policy

Based on the server context (Filesystem Watcher MCP) and sibling tools (list_active_watches, poll_events, unwatch), 'watch_directory' most likely registers a directory to be monitored for filesystem events. This is a read/observe operation — it sets up a watcher but does not itself modify, delete, or execute anything. However, the empty description lowers confidence.

From the tool's definition Tool name 'watch_directory' on a server described as watching directories for live filesystem changes; description is empty and uninformative.

Questions about watch_directory

What does the watch_directory tool do? +

watch_directory. It is categorised as a Read tool in the Filesystem Watcher MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on watch_directory? +

Register the Filesystem Watcher MCP server in PolicyLayer and add a rule for watch_directory: 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 Filesystem Watcher MCP. Nothing to install.

What risk level is watch_directory? +

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

Can I rate-limit watch_directory? +

Yes. Add a rate_limit block to the watch_directory 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 watch_directory completely? +

Set action: deny in the PolicyLayer policy for watch_directory. 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 watch_directory? +

watch_directory is provided by the Filesystem Watcher MCP server (trycatchkamal/filesystemwatcher-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

watch_directory is one line of Filesystem Watcher's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

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.