Get details of a specific watcher including conditions, status, match count, and config.
AI agents call get_watcher to retrieve information from LiveTap without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns information about an existing watcher's configuration and state. There are no side effects, no data modification, no code execution, and no destructive operations. It is a straightforward information-retrieval operation with minimal risk if called arbitrarily.
From the tool's definition Tool is named 'get_watcher' and described as retrieving 'details of a specific watcher including conditions, status, match count, and config.' The verb 'get' and the action of retrieving read-only information with no modification capability indicate a data…
Documented attack patterns abuse exactly the kind of access get_watcher gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LiveTap, and nothing reaches the server without passing your rules. This is the rule we recommend for get_watcher:
{
"version": "1",
"default": "deny",
"tools": {
"get_watcher": {}
}
}get_watcher 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.
Get details of a specific watcher including conditions, status, match count, and config. It is categorised as a Read tool in the LiveTap MCP Server, which means it retrieves data without modifying state.
Register the LiveTap MCP server in PolicyLayer and add a rule for get_watcher: 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 LiveTap. Nothing to install.
get_watcher 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 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. 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 is provided by the LiveTap MCP server (livetap/livetap). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from LiveTap, 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.
13 LiveTap tools catalogued and risk-classified — across an index of 43,000+ MCP servers.