Fetch a workflow summary from n8n by workflow ID.
AI agents call get_workflow_summary to retrieve information from N8n Workflow Tester Safe without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and queries workflow metadata/summary information. The verb 'Fetch' and the read-only nature of obtaining a summary (no creation, modification, deletion, or code execution) clearly place this in the Read category. The safety-first design context and absence of write/execute capabilities further support low severity.
From the tool's definition Tool name 'get_workflow_summary' and description 'Fetch a workflow summary from n8n by workflow ID' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Fetch a workflow summary from n8n by workflow ID. It is categorised as a Read tool in the N8n Workflow Tester Safe MCP Server, which means it retrieves data without modifying state.
Register the N8n Workflow Tester Safe MCP server in PolicyLayer and add a rule for get_workflow_summary: 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 Tester Safe. Nothing to install.
get_workflow_summary 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_workflow_summary 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_workflow_summary. 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_workflow_summary is provided by the N8n Workflow Tester Safe MCP server (souzix76/n8n-workflow-tester-safe). 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 →