favorite_custom_node
Add or remove a custom node from your favorites.
This record as markdown: /tools/flowdot-llc-mcp-server/favorite-custom-node.md
What favorite_custom_node does on FlowDot MCP Server
AI agents use favorite_custom_node 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 favorite_custom_node is rated Medium
This tool modifies a user preference (favorites list) by adding or removing items. It is a reversible write operation with minimal blast radius — no data is deleted, no code is executed, and no financial action is taken.
From the tool's definition Add or remove a custom node from your favorites
Attacks that exploit this kind of access
The rule that runs favorite_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 favorite_custom_node, this is the rule to start with:
favorite_custom_node 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 favorite_custom_node call is checked against it from then on.
Questions about favorite_custom_node
Add or remove a custom node from your favorites. 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 favorite_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.
favorite_custom_node 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 favorite_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.
Set action: deny in the PolicyLayer policy for favorite_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.
favorite_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.
More on FlowDot MCP Server, and thousands of servers like it.
This server
Across the catalogue