AI agents call get_api_endpoint_detail 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 is a straightforward read operation that retrieves and returns details about an existing API endpoint. It queries data without side effects, matching the Read category definition (get, fetch). No data is created, modified, deleted, or executed. Severity is low because exposing API endpoint details is a low-risk information disclosure with limited blast radius.
From the tool's definition Tool name 'get_api_endpoint_detail' and description '获取 HTTP 接口的详细信息' (Get detailed information about HTTP interface) indicate retrieval of existing API endpoint metadata without modification or execution.
Documented attack patterns abuse exactly the kind of access get_api_endpoint_detail 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 get_api_endpoint_detail:
{
"version": "1",
"default": "deny",
"tools": {
"get_api_endpoint_detail": {}
}
}get_api_endpoint_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.
获取 HTTP 接口的详细信息。. 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 get_api_endpoint_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 MCP Server. Nothing to install.
get_api_endpoint_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_endpoint_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_endpoint_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_endpoint_detail 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.