AI agents use preview_blacklist_add 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.
The tool appears to preview adding entries to a blacklist, which modifies security device configuration reversibly. While the description is empty, the name and server context indicate it performs write operations on security policies. Classified as Write rather than Execute because it previews/stages changes rather than immediately executing them.
From the tool's definition Tool name 'preview_blacklist_add' and server context indicating 'device blocking and unblocking operations'. Sibling tool 'apply_blacklist_add' suggests this is a preview/staging operation for blacklist modifications.
Attacks that exploit this kind of access
preview_blacklist_add. 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 preview_blacklist_add: 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.
preview_blacklist_add 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 preview_blacklist_add 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 preview_blacklist_add. 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.
preview_blacklist_add 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 →