AI agents use add_tag_to_api to create or update resources in Apifox MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Apifox MCP Server environment.
This tool creates or modifies metadata (tags) associated with API endpoints without deleting or permanently altering the underlying endpoints or data. Tags are typically reversible and can be removed or modified. The sibling tools include both destructive operations (delete_api_endpoint, delete_folder) and non-destructive ones (create_api_endpoint, create_schema), positioning this tool in the Write category.
From the tool's definition Tool adds tags to existing API endpoints ("为现有接口添加标签" = "add tags to existing interfaces"). This is a reversible data modification operation. The description confirms the operation targets existing API resources by modifying their metadata.
Documented attack patterns abuse exactly the kind of access add_tag_to_api 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 add_tag_to_api:
{
"version": "1",
"default": "deny",
"tools": {
"add_tag_to_api": {
"limits": [
{
"counter": "add_tag_to_api_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_tag_to_api stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
为现有接口添加标签。. It is categorised as a Write tool in the Apifox MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Apifox MCP Server MCP server in PolicyLayer and add a rule for add_tag_to_api: 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.
add_tag_to_api 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 add_tag_to_api 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 add_tag_to_api. 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.
add_tag_to_api 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.