AI agents call get_property_dependencies to retrieve information from n8n-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about n8n node properties and their conditional visibility rules. It performs inspection and introspection—classic read operations that have no side effects, do not execute workflows, do not delete data, and do not commit financial transactions. The mention of 'test visibility with optional config' indicates validation/inspection of existing state, not modification or execution.
From the tool's definition Tool describes property dependencies and visibility rules; it retrieves and displays information about how node properties behave conditionally.
Attacks that exploit this kind of access
Shows property dependencies and visibility rules. Example: sendBody=true reveals body fields. Test visibility with optional config. It is categorised as a Read tool in the n8n-MCP MCP Server, which means it retrieves data without modifying state.
Register the n8n- MCP server in PolicyLayer and add a rule for get_property_dependencies: 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-MCP. Nothing to install.
get_property_dependencies 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_property_dependencies 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_property_dependencies. 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_property_dependencies is provided by the n8n- MCP server (mohsin-zaheer/mcp-server). 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 →