AI agents call yapi_get_categories 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.
This tool retrieves and lists existing API categories and their associated interface information. It performs a read-only query operation with no side effects—no data is created, modified, deleted, or executed. The action is informational only, making it a standard Read category tool with low severity impact.
From the tool's definition Tool name 'yapi_get_categories' and description '获取YApi项目下的接口分类列表，以及每个分类下的接口信息' (Get the interface category list under YApi project and interface information under each category) indicate retrieval of existing API documentation metadata without modification.
Documented attack patterns abuse exactly the kind of access yapi_get_categories gives an agent:
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_get_categories:
{
"version": "1",
"default": "deny",
"tools": {
"yapi_get_categories": {}
}
}yapi_get_categories is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
获取YApi项目下的接口分类列表，以及每个分类下的接口信息. It is categorised as a Read tool in the Yapi Auto MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Yapi Auto MCP Server MCP server in PolicyLayer and add a rule for yapi_get_categories: 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.
yapi_get_categories 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_categories 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_categories. 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_categories 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.
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.