get_custom_node

Get detailed information about a custom node including inputs, outputs, properties, and script code.

SERVERFlowDot MCP Server SOURCEflowdot-llc/mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/flowdot-llc-mcp-server/get-custom-node.md

WHAT IT DOES

What get_custom_node does on FlowDot MCP Server

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

RISK

Why get_custom_node is rated Low

This tool performs a data retrieval operation with no side effects. It fetches and returns information about an existing custom node's configuration and code, but does not execute, modify, delete, or create any data. This is a classic 'Read' category operation.

From the tool's definition Tool name is 'get_custom_node' and description states it retrieves 'detailed information about a custom node including inputs, outputs, properties, and script code.' The verb 'Get' and the retrieval nature of the operation indicate a read-only query with no…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_custom_node 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, this is the rule to start with:

get_custom_node Allowed

get_custom_node is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_custom_node": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect FlowDot MCP Server, apply this rule, and every get_custom_node call is checked against it from then on.

FAQ

Questions about get_custom_node

What does the get_custom_node tool do? +

Get detailed information about a custom node including inputs, outputs, properties, and script code. It is categorised as a Read tool in the FlowDot MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_custom_node? +

Register the FlowDot MCP Server MCP server in PolicyLayer and add a rule for get_custom_node: 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.

What risk level is get_custom_node? +

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

Can I rate-limit get_custom_node? +

Yes. Add a rate_limit block to the get_custom_node 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 get_custom_node completely? +

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

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

KEEP EXPLORING

More on FlowDot MCP Server, and thousands of servers like it.

This server

All 207 FlowDot MCP Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →