Show the status of the embedded watcher that takes periodic non-destructive snapshots while this MCP server is running.
AI agents call watcher_status to retrieve information from Clean Process Ended without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves status information about an embedded watcher component. The description clearly characterizes the watcher's behavior as 'non-destructive snapshots', confirming this is a read-only monitoring tool. No data modification, code execution, deletion, or financial operations are performed. The action is passive inspection, placing it in the Read category with low severity.
From the tool's definition Description explicitly states 'non-destructive snapshots' and 'Show the status', indicating a query/inspection operation with no side effects.
Attacks that exploit this kind of access
Show the status of the embedded watcher that takes periodic non-destructive snapshots while this MCP server is running. It is categorised as a Read tool in the Clean Process Ended MCP Server, which means it retrieves data without modifying state.
Register the Clean Process Ended MCP server in PolicyLayer and add a rule for 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 Clean Process Ended. Nothing to install.
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 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 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.
watcher_status is provided by the Clean Process Ended MCP server (marcelocaporale/clean-process-ended). 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 →