AI agents call watch_for_pattern to retrieve information from Console without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and filters log data based on pattern matching. While it may be used in test automation workflows, the tool itself only reads and streams existing log entries; it does not create, modify, delete, or execute any operations. The pattern matching is a read operation that produces no side effects on the system or data.
From the tool's definition Tool description states it 'stream logs until a pattern is found' and 'wait for a specific log message' - passive monitoring and pattern matching operations with no modification, deletion, or execution of code.
Attacks that exploit this kind of access
Stream logs until a pattern is found. Useful for test automation - start an action, then wait for a specific log message. It is categorised as a Read tool in the Console MCP Server, which means it retrieves data without modifying state.
Register the Console MCP server in PolicyLayer and add a rule for watch_for_pattern: 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 Console. Nothing to install.
watch_for_pattern 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 watch_for_pattern 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 watch_for_pattern. 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.
watch_for_pattern is provided by the Console MCP server (rohithgoud30/console-mcp). 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 →