Get status of the file watcher.
AI agents call get_watcher_status to retrieve information from Codebase Contextifier 9000 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that queries the status of an internal file watcher component. It retrieves information about the indexing system's state (e.g., whether files are being monitored, any active watch processes) but does not create, modify, delete, or execute any operations. The action has no side effects on the codebase or indexing infrastructure.
From the tool's definition Tool name 'get_watcher_status' and description 'Get status of the file watcher' indicate a query operation that retrieves current state information without modifying data or triggering external actions.
Attacks that exploit this kind of access
Get status of the file watcher. It is categorised as a Read tool in the Codebase Contextifier 9000 MCP Server, which means it retrieves data without modifying state.
Register the Codebase Contextifier 9000 MCP server in PolicyLayer and add a rule for get_watcher_status: 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 Codebase Contextifier 9000. Nothing to install.
get_watcher_status 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 get_watcher_status 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 get_watcher_status. 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.
get_watcher_status is provided by the Codebase Contextifier 9000 MCP server (jarmentor/codebase-contextifier-9000). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →