AI agents use apply_blacklist_unblock to create or update resources in AF_MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AF_MCP environment.
This tool creates or modifies data reversibly by removing blacklist entries and changing action status, fitting the Write category. However, it operates on security device configuration with potential high blast radius if misused (could unblock malicious IPs/devices), warranting high severity.
From the tool's definition Tool description states it performs DELETE operations on device blacklist items and updates action status to 'unblocked'. The emergency context (【应急】) and direct manipulation of security device blacklist entries indicate this modifies security-critical state.
Attacks that exploit this kind of access
【应急】解封某一次封禁动作(DELETE 设备黑名单项 + 更新 action 状态为 unblocked)。. It is categorised as a Write tool in the AF_MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AF_ MCP server in PolicyLayer and add a rule for apply_blacklist_unblock: 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.
apply_blacklist_unblock is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the apply_blacklist_unblock 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 apply_blacklist_unblock. 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.
apply_blacklist_unblock 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 →