clone_app
Clone a public app to your library. Creates a private copy that you can customize. The cloned app will: - Be owned by you - Start as private (not published) - Have all the original code and configuration - Not include linked workflows (you
This record as markdown: /tools/flowdot-llc-mcp-server/clone-app.md
What clone_app does on FlowDot MCP Server
AI agents use clone_app 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 clone_app is rated Medium
This tool creates a new copy of an existing app in the user's library. It is a reversible write operation (the clone can presumably be deleted later). It does not execute code, delete data, or move money. The blast radius is medium since it copies potentially complex app configurations, but misuse is limited to creating unwanted copies.
From the tool's definition Clone a public app to your library. Creates a private copy that you can customize. Be owned by you, Start as private (not published), Have all the original code and configuration
Attacks that exploit this kind of access
The rule that runs clone_app 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 clone_app, this is the rule to start with:
clone_app 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 clone_app call is checked against it from then on.
Questions about clone_app
Clone a public app to your library. Creates a private copy that you can customize. The cloned app will: - Be owned by you - Start as private (not published) - Have all the original code and configuration - Not include linked workflows (you. 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 clone_app: 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.
clone_app 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 clone_app 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 clone_app. 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.
clone_app 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