获取接口菜单（包含分类和接口列表）
AI agents call yapi_interface_list_menu to retrieve information from YAPI 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 lists interface menu data including categories and interface information. It performs a read-only query operation with no side effects, data modification, or code execution. The low severity reflects minimal blast radius if misused by an AI agent—at worst, it exposes API documentation structure that is typically non-sensitive metadata.
From the tool's definition Tool name 'yapi_interface_list_menu' and description '获取接口菜单（包含分类和接口列表）' (Get interface menu containing categories and interface list) indicate retrieval of documentation structure and metadata. No modification, execution, or deletion occurs.
Attacks that exploit this kind of access
获取接口菜单（包含分类和接口列表）. It is categorised as a Read tool in the YAPI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the YAPI MCP Server MCP server in PolicyLayer and add a rule for yapi_interface_list_menu: 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 YAPI MCP Server. Nothing to install.
yapi_interface_list_menu 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 yapi_interface_list_menu 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 yapi_interface_list_menu. 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.
yapi_interface_list_menu is provided by the YAPI MCP Server MCP server (zhhbinn/yapi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →