create_goal
Create a new persistent goal. Goals are long-running objectives managed in the FlowDot Hub. After creating a goal you can: - Add tasks (individual actions the daemon should execute) - Add milestones (progress markers) - Pause, resume, complete, or abandon the goal IMPORTANT: Goals are executed by...
This record as markdown: /tools/flowdot-llc-mcp-server/create-goal.md
What create_goal does on FlowDot MCP Server
AI agents use create_goal 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 create_goal is rated Medium
This tool creates and persists new data (goals) in a reversible manner. While goals can trigger external execution via the CLI daemon, the tool itself only manages goal structure—creation and metadata modification. The execution is delegated to the CLI daemon, not performed by this tool.
From the tool's definition Tool description states 'Create a new persistent goal' and allows subsequent management actions (add tasks, milestones, pause, resume, complete, abandon). This creates new data structures that persist in the FlowDot Hub.
Attacks that exploit this kind of access
The rule that runs create_goal 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 create_goal, this is the rule to start with:
create_goal 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 create_goal call is checked against it from then on.
Questions about create_goal
Create a new persistent goal. Goals are long-running objectives managed in the FlowDot Hub. After creating a goal you can: - Add tasks (individual actions the daemon should execute) - Add milestones (progress markers) - Pause, resume, complete, or abandon the goal IMPORTANT: Goals are executed by the FlowDot CLI daemon, not the MCP server. Use MCP to create and manage goal structure; use the CLI (\. 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 create_goal: 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.
create_goal 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 create_goal 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 create_goal. 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.
create_goal 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