add_custom_node_comment
Add a comment to a custom node. Can also be used to reply to existing comments.
This record as markdown: /tools/flowdot-llc-mcp-server/add-custom-node-comment.md
What add_custom_node_comment does on FlowDot MCP Server
AI agents use add_custom_node_comment 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 add_custom_node_comment is rated Medium
This tool creates new comments (reversible data creation) or replies to existing ones, which is a standard Write operation. Comments can typically be edited or deleted, making this a non-destructive modification. The blast radius is minimal—misuse would result in spam, noise, or unwanted comments rather than data loss or system compromise. Severity is low due to the limited scope and reversibility of the action.
From the tool's definition Tool name 'add_custom_node_comment' and description 'Add a comment to a custom node. Can also be used to reply to existing comments.' indicate creation of new comment data or modification of comment threads.
Attacks that exploit this kind of access
The rule that runs add_custom_node_comment 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 add_custom_node_comment, this is the rule to start with:
add_custom_node_comment 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 add_custom_node_comment call is checked against it from then on.
Questions about add_custom_node_comment
Add a comment to a custom node. Can also be used to reply to existing comments. 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 add_custom_node_comment: 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.
add_custom_node_comment 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 add_custom_node_comment 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 add_custom_node_comment. 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.
add_custom_node_comment 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