📊 Get concise security summary for a workflow.
AI agents call get_security_summary 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 displays security analysis information about an existing workflow. It performs no mutations, deletions, code execution, or financial operations. The analysis itself is informational and does not alter workflow state or configuration. Misuse by an AI agent would be limited to information disclosure, posing minimal blast radius.
From the tool's definition Tool name 'get_security_summary' and description 'Get concise security summary for a workflow' indicates retrieval of security analysis data with no modifications or side effects. The 'Get' verb and 'summary' output confirm read-only query functionality.
Attacks that exploit this kind of access
📊 Get concise security summary for 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_security_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 Builder. Nothing to install.
get_security_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_security_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_security_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_security_summary 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 →