get_apis_by_tag

THE RISK

Low Risk

Why get_apis_by_tag needs a policy

This tool retrieves/queries existing API data filtered by tag. It performs no modifications, deletions, or execution of operations—purely a data lookup. Severity is low because reading API metadata poses minimal risk even if misused by an agent.

From the tool's definition Tool name 'get_apis_by_tag' and description '获取指定标签下的所有接口' (retrieve all APIs under a specified tag) indicate a retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access get_apis_by_tag gives an agent:

POLICY

How to control get_apis_by_tag

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 get_apis_by_tag:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_apis_by_tag": {}
  }
}

get_apis_by_tag is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Apifox MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Apifox MCP Server tools

Destructive delete_api_endpoint 删除 Apifox 项目中的 HTTP 接口。⚠️ 此操作不可撤销！ Destructive delete_folder 删除 Apifox 项目中的目录（标签）。⚠️ 警告: 此操作不可撤销！ Destructive delete_schema 删除数据模型 (Schema)。⚠️ 警告: 此操作不可撤销！ Write add_tag_to_api 为现有接口添加标签。 Write create_api_endpoint create_api_endpoint Write create_folder 在 Apifox 项目中创建新目录（标签）。 Write create_schema 创建新的数据模型 (Schema)。 Write generate_crud_apis generate_crud_apis

All 22 Apifox MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_apis_by_tag

What does the get_apis_by_tag tool do? +

获取指定标签下的所有接口。. It is categorised as a Read tool in the Apifox MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_apis_by_tag? +

Register the Apifox MCP Server MCP server in PolicyLayer and add a rule for get_apis_by_tag: 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.

What risk level is get_apis_by_tag? +

get_apis_by_tag is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_apis_by_tag? +

Yes. Add a rate_limit block to the get_apis_by_tag 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.

How do I block get_apis_by_tag completely? +

Set action: deny in the PolicyLayer policy for get_apis_by_tag. 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.

What MCP server provides get_apis_by_tag? +

get_apis_by_tag 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.

Enforce policy on every Apifox MCP Server tool call.

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.

CHECK YOUR STACK →