n8n_get_workflow_details
Get detailed workflow information including metadata, version, and execution statistics. More comprehensive than get_workflow.
This record as markdown: /tools/aegntic-aegntic-mcp/n8n-get-workflow-details.md
What n8n_get_workflow_details does on Obsidian Elite RAG MCP Server
AI agents call n8n_get_workflow_details to retrieve information from Obsidian Elite RAG MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why n8n_get_workflow_details is rated Low
This tool retrieves and queries workflow information (metadata, version, statistics) from an n8n automation platform. It is explicitly a 'get' operation with no side effects—it does not create, modify, delete, or execute workflows, only reads their details. The 'Read' category is the appropriate classification for data retrieval operations.
From the tool's definition Tool name 'n8n_get_workflow_details' and description 'Get detailed workflow information including metadata, version, and execution statistics' indicate retrieval of existing workflow data with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
The rule that runs n8n_get_workflow_details safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Obsidian Elite RAG MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For n8n_get_workflow_details, this is the rule to start with:
n8n_get_workflow_details is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Obsidian Elite RAG MCP Server, apply this rule, and every n8n_get_workflow_details call is checked against it from then on.
Questions about n8n_get_workflow_details
Get detailed workflow information including metadata, version, and execution statistics. More comprehensive than get_workflow. It is categorised as a Read tool in the Obsidian Elite RAG MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Obsidian Elite RAG MCP Server MCP server in PolicyLayer and add a rule for n8n_get_workflow_details: 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 Obsidian Elite RAG MCP Server. Nothing to install.
n8n_get_workflow_details 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 n8n_get_workflow_details 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 n8n_get_workflow_details. 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.
n8n_get_workflow_details is provided by the Obsidian Elite RAG MCP Server MCP server (aegntic/aegntic-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Obsidian Elite RAG MCP Server, and thousands of servers like it.
This server
Across the catalogue