AI agents use create_schema to create or update resources in Apifox MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Apifox MCP Server environment.
This tool creates new schemas, which is a data modification that can be undone (schemas can be deleted or updated). It does not execute arbitrary code, delete data irreversibly, or involve financial transactions. The blast radius is moderate—a malicious agent could add invalid or malicious schemas to an API project, causing API validation failures or confusion, but the effect is reversible.
From the tool's definition Tool description states '创建新的数据模型 (Schema)' (create new data model/schema). The action is creation of a data structure, which is a reversible write operation.
Documented attack patterns abuse exactly the kind of access create_schema gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Apifox MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_schema:
{
"version": "1",
"default": "deny",
"tools": {
"create_schema": {
"limits": [
{
"counter": "create_schema_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_schema 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.
Free to start. No card required.
创建新的数据模型 (Schema)。. It is categorised as a Write tool in the Apifox MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Apifox MCP Server MCP server in PolicyLayer and add a rule for create_schema: 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 Apifox MCP Server. Nothing to install.
create_schema 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 create_schema 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 create_schema. 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.
create_schema is provided by the Apifox MCP Server MCP server (iwen-conf/apifox-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Apifox 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.
22 Apifox MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.