toggle_custom_node_visibility

Change the visibility of a custom node (private, public, or unlisted).

SERVERFlowDot MCP Server SOURCEflowdot-llc/mcp-server
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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)

Questions about toggle_custom_node_visibility

What does the toggle_custom_node_visibility tool do? +

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.

How do I enforce a policy on toggle_custom_node_visibility? +

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.

What risk level is toggle_custom_node_visibility? +

toggle_custom_node_visibility is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit toggle_custom_node_visibility? +

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.

How do I block toggle_custom_node_visibility completely? +

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.

What MCP server provides toggle_custom_node_visibility? +

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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of FlowDot MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.