获取接口详情，可直接传入 YAPI 接口页面 URL 自动解析参数
AI agents call yapi_interface_get 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 returns interface details from YAPI documentation. It performs data lookup and parsing without modifying, deleting, or executing any operations. The capability to extract parameters from a URL is informational retrieval only. This is a classic Read category operation—it queries data with no side effects.
From the tool's definition Tool name 'yapi_interface_get' and description '获取接口详情' (get interface details) indicates retrieval of API interface information.
Attacks that exploit this kind of access
获取接口详情，可直接传入 YAPI 接口页面 URL 自动解析参数. 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_get: 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_get 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_get 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_get. 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_get 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 →