Get full fabric status (n8n + Qdrant + Redis)
AI agents call fabric_status to retrieve information from N8n Fabric without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves status information about the underlying infrastructure components. It performs no write, deletion, execution, or financial operations. The blast radius of misuse is minimal—an agent could potentially infer system architecture or availability but cannot modify data, execute workflows, or cause harm. This is a standard Read category operation.
From the tool's definition Tool name 'fabric_status' and description 'Get full fabric status' indicate retrieval of system status information with no modification capabilities. The action is purely informational (get), querying the state of n8n, Qdrant, and Redis components.
Attacks that exploit this kind of access
Get full fabric status (n8n + Qdrant + Redis). It is categorised as a Read tool in the N8n Fabric MCP Server, which means it retrieves data without modifying state.
Register the N8n Fabric MCP server in PolicyLayer and add a rule for fabric_status: 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 Fabric. Nothing to install.
fabric_status 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 fabric_status 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 fabric_status. 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.
fabric_status is provided by the N8n Fabric MCP server (ry-ops/n8n-fabric). 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 →