Remove a command from the registry by ID or alias
AI agents call afc-remove-command to permanently remove resources in AFC Commander (Free Edition) — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a command from the registry deletes stored configuration that cannot be recovered without external backups. This is a destructive operation with no undo mechanism.
From the tool's definition Tool name and description: 'Remove a command from the registry by ID or alias' — the verb 'remove' combined with deletion from a persistent registry is irreversible data loss.
Attacks that exploit this kind of access
Remove a command from the registry by ID or alias. It is categorised as a Destructive tool in the AFC Commander (Free Edition) MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the AFC Commander (Free Edition) MCP server in PolicyLayer and add a rule for afc-remove-command: 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 AFC Commander (Free Edition). Nothing to install.
afc-remove-command 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 afc-remove-command 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 afc-remove-command. 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.
afc-remove-command is provided by the AFC Commander (Free Edition) MCP server (trace186/afc-commander-cli-registry-with-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 →