AI agents use create_api_endpoint 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.
Creating an API endpoint modifies the project configuration by adding a new resource definition. This is a Write category action (creates data reversibly). Severity is medium because an AI agent could create malicious endpoints, expose unintended APIs, or clutter the project, but effects are reversible via the paired delete_api_endpoint tool.
From the tool's definition Tool name 'create_api_endpoint' combined with server description stating it 'manage[s] Apifox API projects, including listing, creating, updating, and deleting API endpoints and schemas' indicates this tool creates new API endpoints, which is a reversible…
Documented attack patterns abuse exactly the kind of access create_api_endpoint 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_api_endpoint:
{
"version": "1",
"default": "deny",
"tools": {
"create_api_endpoint": {
"limits": [
{
"counter": "create_api_endpoint_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_api_endpoint 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.
create_api_endpoint. 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_api_endpoint: 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_api_endpoint 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_api_endpoint 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_api_endpoint. 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_api_endpoint 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.