👁️ Monitor workflow execution and get detailed error feedback. Returns execution status with error analysis if execution failed.
AI agents call watch_workflow_execution to retrieve information from n8n Workflow Builder without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and reports on workflow execution status and error information. It observes and analyzes existing execution data but does not create, modify, delete, or trigger execution of workflows. The monitoring and analysis of execution state constitutes a Read operation with minimal security risk.
From the tool's definition Tool description states it 'Monitor workflow execution and get detailed error feedback' and 'Returns execution status with error analysis if execution failed.' The verb 'monitor' and 'returns' indicate read-only observation of execution state without…
Attacks that exploit this kind of access
👁️ Monitor workflow execution and get detailed error feedback. Returns execution status with error analysis if execution failed. It is categorised as a Read tool in the n8n Workflow Builder MCP Server, which means it retrieves data without modifying state.
Register the n8n Workflow Builder MCP server in PolicyLayer and add a rule for watch_workflow_execution: 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 n8n Workflow Builder. Nothing to install.
watch_workflow_execution 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_workflow_execution 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_workflow_execution. 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_workflow_execution is provided by the n8n Workflow Builder MCP server (schimmilab/n8n-workflow-builder). 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 →