delete_agent_character
Permanently delete an agent character. Requires confirm: true. This is irreversible — any voice-call session in flight will fail with a 404 on its character lookup.
This record as markdown: /tools/flowdot-llc-mcp-server/delete-agent-character.md
What delete_agent_character does on FlowDot MCP Server
AI agents call delete_agent_character to permanently remove resources in FlowDot MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_agent_character is rated Critical
The tool irreversibly deletes an agent character and causes active sessions to fail. The description explicitly states 'Permanently delete' and 'This is irreversible', combined with the impact on in-flight operations. While it requires explicit confirmation, deletion is the core destructive action.
From the tool's definition Permanently delete an agent character. Requires confirm: true. This is irreversible — any voice-call session in flight will fail with a 404 on its character lookup.
Attacks that exploit this kind of access
The rule that runs delete_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 delete_agent_character, this is the rule to start with:
delete_agent_character is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect FlowDot MCP Server, apply this rule, and every delete_agent_character call is checked against it from then on.
Questions about delete_agent_character
Permanently delete an agent character. Requires confirm: true. This is irreversible — any voice-call session in flight will fail with a 404 on its character lookup. It is categorised as a Destructive tool in the FlowDot MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the FlowDot MCP Server MCP server in PolicyLayer and add a rule for delete_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.
delete_agent_character is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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.
Across the catalogue