获取接口详情,支持格式:数字ID
AI agents call yapi-get-interface 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 API interface details by ID. It performs a read-only query operation with no capability to modify, delete, or execute anything. The blast radius of misuse is minimal—an attacker could only view interface documentation that may or may not be sensitive, but cannot alter it or trigger operations.
From the tool's definition Tool name is 'yapi-get-interface' and description states '获取接口详情,支持格式:数字ID' which translates to 'Get interface details, supports format: numeric ID'. This is a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
获取接口详情,支持格式:数字ID. 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-get-interface: 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-get-interface 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-get-interface 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-get-interface. 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-get-interface is provided by the YAPI MCP Server MCP server (w-abel-jia/yapi-interface-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 →