📜 Get a list of recently accessed workflows.
AI agents call get_recent_workflows 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 metadata about recently accessed workflows. It queries existing data without modifying, executing, or deleting anything. The only potential risk is information disclosure if workflow names or access patterns are sensitive, but this is a standard read operation. No destructive, executable, or financial operations are involved.
From the tool's definition Tool name 'get_recent_workflows' and description 'Get a list of recently accessed workflows' both indicate a retrieval operation with no side effects. The verb 'Get' and 'list' are characteristic of Read operations.
Attacks that exploit this kind of access
📜 Get a list of recently accessed workflows. 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 get_recent_workflows: 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.
get_recent_workflows 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_workflows 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_workflows. 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_workflows 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 →