导入接口数据到 YAPI
AI agents use yapi_import_data 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.
This tool imports/uploads interface data into YAPI, which creates or modifies existing documentation records. This is a Write operation (data creation/modification with reversible effects) rather than Destructive (no deletion or irreversible overwriting stated), Execute (not arbitrary code execution), or Read (actively modifies state).
From the tool's definition Tool name 'yapi_import_data' with description '导入接口数据到 YAPI' (Import interface data to YAPI) indicates data creation/modification. The sibling tools include yapi_interface_add, yapi_interface_save, and yapi_interface_up, all of which are Write operations.
Attacks that exploit this kind of access
导入接口数据到 YAPI. 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.
Register the YAPI MCP Server MCP server in PolicyLayer and add a rule for yapi_import_data: 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_import_data is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the yapi_import_data 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_import_data. 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_import_data 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.
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 →