yapi_interface_save · YAPI MCP Server MCP: Risk & Policy

WHAT IT DOES

What yapi_interface_save does on YAPI MCP Server

AI agents use yapi_interface_save to create or update resources in YAPI MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your YAPI MCP Server environment.

WHY IT NEEDS A POLICY

Why yapi_interface_save needs a policy

The tool saves/persists interface data with create or update semantics. While it modifies stored data, it is reversible (can be edited again or deleted by other tools), making it a Write rather than Destructive action. Severity is medium because misuse could corrupt API documentation affecting downstream API consumers, but the blast radius is limited to API metadata rather than production data or code execution.

From the tool's definition Tool name 'yapi_interface_save' combined with description '保存接口（新增或更新）' (Save interface - create or update) explicitly indicates creating or modifying API interface documentation. This is a reversible write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

yapi_interface_save Rate-limited

yapi_interface_save stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "yapi_interface_save": {
      "limits": [
        {
          "counter": "yapi_interface_save_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches YAPI MCP Server, so you can run agents against it safely.

FAQ

Questions about yapi_interface_save

What does the yapi_interface_save tool do? +

保存接口（新增或更新）. It is categorised as a Write tool in the YAPI MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on yapi_interface_save? +

Register the YAPI MCP Server MCP server in PolicyLayer and add a rule for yapi_interface_save: 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.

What risk level is yapi_interface_save? +

yapi_interface_save is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit yapi_interface_save? +

Yes. Add a rate_limit block to the yapi_interface_save 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_interface_save completely? +

Set action: deny in the PolicyLayer policy for yapi_interface_save. 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_interface_save? +

yapi_interface_save 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.