Skip to main content
Glama

n8n_generate_audit

Generate security audits for n8n instances to identify vulnerabilities and ensure compliance with best practices.

Instructions

Generate a security audit for your n8n instance

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
optionsNoAudit options

Implementation Reference

  • Actual implementation of the n8n audit generation, making the API call.
    async generateAudit(options?: any): Promise<any> {
      const response = await this.client.post('/audit', options || {});
      return response.data;
    }
  • Tool handler execution block for n8n_generate_audit.
    case 'n8n_generate_audit': {
      const result = await n8nClient.generateAudit(args?.options);
      return {
        content: [{ type: 'text', text: formatResponse(result) }],
      };
    }
Behavior2/5

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

With no annotations provided, the description carries the full disclosure burden but omits critical behavioral details: output format (JSON, PDF, report?), delivery method (returned value, file download, email?), execution time, or whether this triggers a background job versus immediate response.

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

Conciseness4/5

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

Single sentence of six words is appropriately compact with no filler, though arguably under-loaded given the tool's complexity and lack of supporting annotations or output schema.

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?

Insufficient for a complex diagnostic operation. No output schema exists, yet the description doesn't explain return values, report contents, or side effects. The vague 'options' parameter combined with missing behavioral details leaves significant gaps for an AI attempting to invoke this correctly.

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

Parameters3/5

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

Schema has 100% coverage with one parameter described as 'Audit options', so baseline is 3. The description adds no clarifying details about what specific options are available (scope, depth, format) or their valid values, leaving the parameter effectively undocumented beyond the schema.

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?

States a clear verb ('Generate') and specific resource ('security audit'), making the basic purpose understandable. However, it fails to distinguish from sibling diagnostic tools like 'n8n_health_check' or clarify what constitutes a security audit in this context.

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

Usage Guidelines2/5

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

Provides no guidance on when to invoke this tool versus alternatives like health_check, or prerequisites such as admin permissions typically required for security audits. No 'when-not-to-use' warnings included.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Shravan1610/n8n-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server