AI agents call list_tags to retrieve information from Apifox MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves information about tags and their associated interface counts. It performs a read-only operation with no ability to create, modify, delete, or execute operations. The blast radius of misuse is minimal—an agent could only gain visibility into project organization structure.
From the tool's definition Tool name 'list_tags' and description 'lists all tags in the project and their interface count' indicate retrieval of existing data with no modification or side effects.
Documented attack patterns abuse exactly the kind of access list_tags gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Apifox MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_tags:
{
"version": "1",
"default": "deny",
"tools": {
"list_tags": {}
}
}list_tags is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
列出项目中所有的标签及其接口数量。. It is categorised as a Read tool in the Apifox MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Apifox MCP Server MCP server in PolicyLayer and add a rule for list_tags: 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 Apifox MCP Server. Nothing to install.
list_tags 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 list_tags 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 list_tags. 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.
list_tags is provided by the Apifox MCP Server MCP server (iwen-conf/apifox-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Apifox MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
22 Apifox MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.