AI agents call whitelist_stats to retrieve information from AF_MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves statistical data and status information about whitelist operations. There is no capability to modify, delete, execute commands, or move resources. It is a read-only query operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'whitelist_stats' and description '查询白名单运行统计（命中数、命中率、按层分布）+ 引擎状态' indicate a query/statistics retrieval operation.
Attacks that exploit this kind of access
查询白名单运行统计（命中数、命中率、按层分布）+ 引擎状态。. It is categorised as a Read tool in the AF_MCP MCP Server, which means it retrieves data without modifying state.
Register the AF_ MCP server in PolicyLayer and add a rule for whitelist_stats: 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.
whitelist_stats is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the whitelist_stats 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 whitelist_stats. 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.
whitelist_stats 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 →