清空封锁攻击者记录，并强制要求显式确认。
AI agents call block_clear_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 purges/deletes attacker blocking records from security devices. Such deletion cannot be undone and directly impacts the security posture by removing enforcement records. The explicit confirmation requirement indicates the operation's severity. While this is not a traditional data deletion, it removes security enforcement logs/blocks that protect systems, making it destructive in nature.
From the tool's definition Tool name 'block_clear_attackers' combined with description '清空封锁攻击者记录，并强制要求显式确认' (Clear attacker blocking records and force explicit confirmation). The verb '清空' (clear/purge) indicates irreversible deletion of attacker block 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_clear_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_clear_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_clear_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_clear_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_clear_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 →