获取单个接口的完整文档。 使用指引： - 已经知道接口路径时，直接传 path 获取详情 - 先用 search_api 查到候选，再用本工具精确查看参数/请求体/响应/示例 - method 可选，未提供时返回该 path 下所有方法（如同时存在 GET/POST）
AI agents call get_api_detail to retrieve information from Apifox Filter MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays API documentation details without modifying, executing, deleting, or creating any data. It is a straightforward read operation that fetches metadata about API endpoints. The blast radius is minimal—an AI agent misusing this tool could only retrieve unwanted documentation, not cause operational harm.
From the tool's definition Tool name 'get_api_detail' and description '获取单个接口的完整文档' (get complete documentation for a single interface) indicates retrieval of API documentation.
Documented attack patterns abuse exactly the kind of access get_api_detail gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Apifox Filter MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_api_detail:
{
"version": "1",
"default": "deny",
"tools": {
"get_api_detail": {}
}
}get_api_detail 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.
获取单个接口的完整文档。 使用指引： - 已经知道接口路径时，直接传 path 获取详情 - 先用 search_api 查到候选，再用本工具精确查看参数/请求体/响应/示例 - method 可选，未提供时返回该 path 下所有方法（如同时存在 GET/POST）. It is categorised as a Read tool in the Apifox Filter MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Apifox Filter MCP Server MCP server in PolicyLayer and add a rule for get_api_detail: 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 Filter MCP Server. Nothing to install.
get_api_detail 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 get_api_detail 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 get_api_detail. 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.
get_api_detail is provided by the Apifox Filter MCP Server MCP server (xiaou66/apifox-filter-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Apifox Filter 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.
9 Apifox Filter MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.