批量删除封锁攻击者，并在执行前进行白名单和人工确认校验。
AI agents call block_delete_attackers to permanently remove resources in AF_MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes blocking/blacklist entries for attackers. While it includes safety mechanisms (whitelist checks and manual confirmation), the core operation is destructive—once deleted, the blocking records cannot be recovered without manual re-entry. Destructive category is more severe than Write (which covers reversible modifications) because data loss is permanent.
From the tool's definition Tool name 'block_delete_attackers' and description '批量删除封锁攻击者' (bulk delete blocked attackers) indicates irreversible deletion of blocking records.
Attacks that exploit this kind of access
批量删除封锁攻击者，并在执行前进行白名单和人工确认校验。. It is categorised as a Destructive tool in the AF_MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the AF_ MCP server in PolicyLayer and add a rule for block_delete_attackers: 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 AF_MCP. Nothing to install.
block_delete_attackers 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 block_delete_attackers 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 block_delete_attackers. 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.
block_delete_attackers is provided by the AF_ MCP server (xiaqijun/af_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 →