AI agents call get_n8n_status to retrieve information from Spline without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries the current status of n8n integration without creating, modifying, deleting, or executing any operations. It is purely informational and has no blast radius if invoked by an AI agent.
From the tool's definition Tool name 'get_n8n_status' and description 'Get n8n integration status' indicate a status query operation with no side effects.
Attacks that exploit this kind of access
Get n8n integration status. It is categorised as a Read tool in the Spline MCP Server, which means it retrieves data without modifying state.
Register the Spline MCP server in PolicyLayer and add a rule for get_n8n_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 Spline. Nothing to install.
get_n8n_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 get_n8n_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 get_n8n_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.
get_n8n_status is provided by the Spline MCP server (lesleslie/spline-mcp). 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 →