duplicate_agent_character
Duplicate one of your own agent characters. Unlike fork, this copies the full LLM choice as well — useful for spinning up a variant.
This record as markdown: /tools/flowdot-llc-mcp-server/duplicate-agent-character.md
What duplicate_agent_character does on FlowDot MCP Server
AI agents use duplicate_agent_character 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 duplicate_agent_character is rated Medium
This tool creates a new copy of an existing agent character, which is a reversible write/create operation. It does not delete or overwrite existing data, execute code, or involve financial transactions. The blast radius is medium since duplicating agent characters could spin up unintended variants or consume platform resources if misused.
From the tool's definition Duplicate one of your own agent characters... this copies the full LLM choice as well — useful for spinning up a variant.
Attacks that exploit this kind of access
The rule that runs duplicate_agent_character 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 duplicate_agent_character, this is the rule to start with:
duplicate_agent_character 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 duplicate_agent_character call is checked against it from then on.
Questions about duplicate_agent_character
Duplicate one of your own agent characters. Unlike fork, this copies the full LLM choice as well — useful for spinning up a variant. 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 duplicate_agent_character: 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.
duplicate_agent_character 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 duplicate_agent_character 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 duplicate_agent_character. 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.
duplicate_agent_character 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