📋 Get all intent metadata from a workflow.
AI agents call get_workflow_intents 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 queries intent metadata from an existing workflow. The verb 'Get' combined with the descriptive context of the n8n Workflow Builder (which provides analysis and monitoring capabilities) indicates a read-only operation with no side effects. It does not execute workflows, modify data, delete resources, or commit financial transactions.
From the tool's definition Tool name 'get_workflow_intents' and description 'Get all intent metadata from a workflow' indicate a retrieval operation that queries and returns metadata without modification or execution of the workflow itself.
Attacks that exploit this kind of access
📋 Get all intent metadata from a workflow. 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_workflow_intents: 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_workflow_intents 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_intents 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_intents. 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_intents 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 →