Low Risk

yapi_search_apis

搜索YApi中的接口

How to control yapi_search_apis ↓

What yapi_search_apis does on Yapi Auto MCP Server

AI agents call yapi_search_apis to retrieve information from Yapi Auto MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why yapi_search_apis needs a policy

This tool searches and retrieves API information from the YApi platform. Search operations are inherently read-only with no side effects. The sibling tools include write operations (yapi_save_api) and other reads (yapi_get_api_desc, yapi_get_categories, yapi_list_projects), confirming this one is clearly a read operation.

From the tool's definition Tool name 'yapi_search_apis' and description '搜索YApi中的接口' (search APIs in YApi) indicate a search/query operation that retrieves API documentation without modifying data.

Documented attack patterns abuse exactly the kind of access yapi_search_apis gives an agent:

How to control yapi_search_apis

PolicyLayer is an MCP gateway — it sits between your AI agents and Yapi Auto MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for yapi_search_apis:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "yapi_search_apis": {}
  }
}

yapi_search_apis is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Yapi Auto MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about yapi_search_apis

What does the yapi_search_apis tool do? +

搜索YApi中的接口. It is categorised as a Read tool in the Yapi Auto MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on yapi_search_apis? +

Register the Yapi Auto MCP Server MCP server in PolicyLayer and add a rule for yapi_search_apis: 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 Auto MCP Server. Nothing to install.

What risk level is yapi_search_apis? +

yapi_search_apis is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit yapi_search_apis? +

Yes. Add a rate_limit block to the yapi_search_apis 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.

How do I block yapi_search_apis completely? +

Set action: deny in the PolicyLayer policy for yapi_search_apis. 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.

What MCP server provides yapi_search_apis? +

yapi_search_apis is provided by the Yapi Auto MCP Server MCP server (lzsheng/yapi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Yapi Auto MCP Server tool call.

Start from Yapi Auto 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.

5 Yapi Auto MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.