toggle_custom_node_visibility
Change the visibility of a custom node (private, public, or unlisted).
This record as markdown: /tools/flowdot-llc-mcp-server/toggle-custom-node-visibility.md
What toggle_custom_node_visibility does on FlowDot MCP Server
AI agents use toggle_custom_node_visibility to create or update resources in FlowDot MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FlowDot MCP Server environment.
Why toggle_custom_node_visibility is rated Medium
This tool modifies a setting (visibility) on a custom node. It is reversible — you can toggle between private, public, and unlisted states — so it falls under Write rather than Destructive. However, making a node public could expose sensitive logic or data to unintended audiences, giving it a medium severity blast radius if misused.
From the tool's definition Change the visibility of a custom node (private, public, or unlisted)
Attacks that exploit this kind of access
The rule that runs toggle_custom_node_visibility 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 toggle_custom_node_visibility, this is the rule to start with:
toggle_custom_node_visibility stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 toggle_custom_node_visibility call is checked against it from then on.
Questions about toggle_custom_node_visibility
Change the visibility of a custom node (private, public, or unlisted). It is categorised as a Write tool in the FlowDot MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the FlowDot MCP Server MCP server in PolicyLayer and add a rule for toggle_custom_node_visibility: 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.
toggle_custom_node_visibility is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the toggle_custom_node_visibility 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 toggle_custom_node_visibility. 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.
toggle_custom_node_visibility 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