Remove a variant from a family (soft-deletes its materialized agent). Cannot remove the entry
AI agents call remove_family_variant to permanently remove resources in BotUyo MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs a deletion operation on agent variants. Although the description specifies 'soft-delete' (which theoretically allows recovery), the functional outcome is removal of a materialized agent from the system.
From the tool's definition Tool description states 'soft-deletes its materialized agent' and 'Remove a variant from a family'. The action irreversibly removes an agent variant, which is a destructive operation that cannot be undone based on the context of agent management systems.
Attacks that exploit this kind of access
Remove a variant from a family (soft-deletes its materialized agent). Cannot remove the entry. It is categorised as a Destructive tool in the BotUyo MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the BotUyo MCP Server MCP server in PolicyLayer and add a rule for remove_family_variant: 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 BotUyo MCP Server. Nothing to install.
remove_family_variant 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 remove_family_variant 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 remove_family_variant. 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.
remove_family_variant is provided by the BotUyo MCP Server MCP server (marcoar1/botuyo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →