AI agents call get_recent_errors to retrieve information from VibeWatch 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 existing terminal error output for display purposes. It has no side effects—it does not execute commands, modify state, delete data, or trigger external operations. The narrow scope (recent errors only) and read-only nature make it a low-risk Read operation. Severity is low because misuse would only expose existing error information already present on the system.
From the tool's definition Tool name 'get_recent_errors' and description 'Get only recent error lines from the terminal output' indicate data retrieval with no modification. The verb 'Get' and context of querying terminal history confirms read-only behavior.
Attacks that exploit this kind of access
Get only recent error lines from the terminal output. This is a quick way to see what went wrong without scrolling through all output. It is categorised as a Read tool in the VibeWatch MCP Server, which means it retrieves data without modifying state.
Register the VibeWatch MCP server in PolicyLayer and add a rule for get_recent_errors: 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 VibeWatch. Nothing to install.
get_recent_errors 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_recent_errors 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_recent_errors. 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_recent_errors is provided by the VibeWatch MCP server (krjordan/vibewatch). 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 →