Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

n8n: Run security audit

n8n_run_security_audit
Destructive

Run a security audit on your n8n instance to get diagnostics grouped by category. Use it to identify configuration and access risks across optional audit categories.

Instructions

[UNIFIED] Run a security audit on the n8n instance. Returns security diagnostics grouped by category. All parameters are OPTIONAL.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site": "<site>"
    },
    "name": "n8n_run_security_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
categoriesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0
  2. Removedv3.13.1
  3. First observedv3.4.0

TDQS

C2.7/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description adds only the behavioral detail that diagnostics are returned and grouped by category. Given destructiveHint=true, readOnlyHint=false, and idempotentHint=false, it critically fails to explain what could be changed or destroyed, whether rerunning is safe, or why a diagnostic audit carries these risks.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loads the action and result, making it easy to scan. However, "[UNIFIED]" is unexplained and the final sentence is inaccurate; that space would be better used to document the required input and significant safety behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The basic purpose and result are present, but important invocation and safety information is missing for a two-parameter tool with no schema descriptions or output schema. The required-parameter contradiction, undocumented category selection, and unexplained destructive annotations leave substantial risk of incorrect or unsafe invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description explains neither the required site value nor the categories input, including site format, valid category values, or the effect of null. Worse, "All parameters are OPTIONAL" directly contradicts the schema's required site field, making its only explicit parameter guidance misleading.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly specifies the action ("Run a security audit"), the target ("the n8n instance"), and the result (security diagnostics grouped by category). It does not explicitly differentiate this instance security audit from siblings such as get_audit_log or the WordPress audit-hook tools, so its routing clarity is good rather than exceptional.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The wording implies using the tool when instance-wide n8n security diagnostics are needed, potentially for selected categories. It provides no explicit prerequisites, when-not guidance, or conditions for choosing an alternative audit-related tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools