get_custom_node_template
Generate a working script template for a custom node based on inputs and outputs. Use this tool to get a correctly formatted script before creating a custom node. The generated template includes: - The required processData(inputs, properties, llm) function - Input variable declarations with prope...
This record as markdown: /tools/flowdot-llc-mcp-server/get-custom-node-template.md
What get_custom_node_template does on FlowDot MCP Server
AI agents call get_custom_node_template to retrieve information from FlowDot MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_custom_node_template is rated Low
This is a read-only tool that retrieves/generates template data. While it produces script code, it does not execute that code, modify platform state, or trigger external operations. The template is informational and must be explicitly used by the user to create a custom node in a separate step. No side effects occur from calling this tool alone.
From the tool's definition Tool generates and returns a template script; it does not modify, delete, execute, or commit any operations.
Attacks that exploit this kind of access
The rule that runs get_custom_node_template safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FlowDot MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_custom_node_template, this is the rule to start with:
get_custom_node_template is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect FlowDot MCP Server, apply this rule, and every get_custom_node_template call is checked against it from then on.
Questions about get_custom_node_template
Generate a working script template for a custom node based on inputs and outputs. Use this tool to get a correctly formatted script before creating a custom node. The generated template includes: - The required processData(inputs, properties, llm) function - Input variable declarations with proper defaults - Property access (if properties defined) - LLM call examples (if llm_enabled is true) - Return statement with all output names VALID DATA TYPES: text, number, boolean, json, array, any LLM CAPABILITY: Set llm_enabled: true to generate a template that includes llm.call() examples. When LLM is enabled, users will see Quick Select buttons to choose their AI model. It is categorised as a Read tool in the FlowDot MCP Server MCP Server, which means it retrieves data without modifying state.
Register the FlowDot MCP Server MCP server in PolicyLayer and add a rule for get_custom_node_template: 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 FlowDot MCP Server. Nothing to install.
get_custom_node_template 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_custom_node_template 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_custom_node_template. 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_custom_node_template is provided by the FlowDot MCP Server MCP server (flowdot-llc/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FlowDot MCP Server, and thousands of servers like it.
This server
Across the catalogue