analyze_intent_coverage

πŸ“Š Analyze how well a workflow is documented with intent metadata.

Server n8n Workflow Builder schimmilab/n8n-workflow-builder
Category Read
Risk class Low
Parameters 00 required

What analyze_intent_coverage does on n8n Workflow Builder

AI agents call analyze_intent_coverage 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.

Why analyze_intent_coverage needs a policy

This tool retrieves and examines intent metadata coverage in workflows to provide analysis feedback. It performs inspection only with no side effects, state changes, or external operation triggers. The blast radius of misuse is minimalβ€”at worst, an AI agent could retrieve accurate documentation metrics unnecessarily, which causes no harm.

From the tool's definition Tool name contains 'analyze' and description states it analyzes workflow documentation; the verb 'analyze' indicates passive inspection/querying of existing metadata without modification or execution.

Questions about analyze_intent_coverage

What does the analyze_intent_coverage tool do? +

πŸ“Š Analyze how well a workflow is documented with intent metadata. It is categorised as a Read tool in the n8n Workflow Builder MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on analyze_intent_coverage? +

Register the n8n Workflow Builder MCP server in PolicyLayer and add a rule for analyze_intent_coverage: 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.

What risk level is analyze_intent_coverage? +

analyze_intent_coverage is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit analyze_intent_coverage? +

Yes. Add a rate_limit block to the analyze_intent_coverage 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.

How do I block analyze_intent_coverage completely? +

Set action: deny in the PolicyLayer policy for analyze_intent_coverage. 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.

What MCP server provides analyze_intent_coverage? +

analyze_intent_coverage 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.

// THE FULL RECORD

analyze_intent_coverage is one line of n8n Workflow Builder's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy β€” re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.