AI agents call yapi_get_interface_by_url to retrieve information from Mcp Yapi without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves API documentation and interface details from a YApi server. It performs a read-only query operation—fetching structured data about API endpoints and their specifications. There are no side effects, no code execution, no data modification, and no destructive actions.
From the tool's definition Tool name 'yapi_get_interface_by_url' and description indicate it retrieves detailed information about an API interface from YApi by URL.
Attacks that exploit this kind of access
通过YApi接口URL获取详细信息。支持直接粘贴YApi链接,如: https://yapi.example.com/project/100/interface/api/12345. It is categorised as a Read tool in the Mcp Yapi MCP Server, which means it retrieves data without modifying state.
Register the Mcp Yapi MCP server in PolicyLayer and add a rule for yapi_get_interface_by_url: 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 Mcp Yapi. Nothing to install.
yapi_get_interface_by_url 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_by_url 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_by_url. 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_by_url is provided by the Mcp Yapi MCP server (tstonelee/mcp-yapi-server). 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 →