favorite_workflow
Add or remove a workflow from your favorites. Favorited workflows can be filtered in list_workflows.
This record as markdown: /tools/flowdot-llc-mcp-server/favorite-workflow.md
What favorite_workflow does on FlowDot MCP Server
AI agents use favorite_workflow 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_workflow is rated Medium
This tool modifies user preference data (favorites list) in a reversible way — adding or removing a workflow from favorites. It has no destructive effects, no financial implications, and no code execution. The blast radius of misuse is minimal as it only affects the user's own favorites list.
From the tool's definition Add or remove a workflow from your favorites
Attacks that exploit this kind of access
The rule that runs favorite_workflow 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_workflow, this is the rule to start with:
favorite_workflow 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_workflow call is checked against it from then on.
Questions about favorite_workflow
Add or remove a workflow from your favorites. Favorited workflows can be filtered in list_workflows. 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_workflow: 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_workflow 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_workflow 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_workflow. 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_workflow 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