AI agents use apipost_create_folder to create or update resources in ApiPost MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ApiPost MCP environment.
This tool creates folders within the ApiPost documentation hierarchy, which is a reversible write operation. It adds new organizational containers to the documentation structure without executing external code, deleting data, or moving money.
From the tool's definition Tool name 'apipost_create_folder' and description indicate it creates a new folder/directory in the API documentation system. Chinese description '创建API文档目录' translates to 'create API documentation folder'.
Documented attack patterns abuse exactly the kind of access apipost_create_folder gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ApiPost MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for apipost_create_folder:
{
"version": "1",
"default": "deny",
"tools": {
"apipost_create_folder": {
"limits": [
{
"counter": "apipost_create_folder_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}apipost_create_folder 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.
创建API文档目录，支持在指定父目录下创建新的文件夹. It is categorised as a Write tool in the ApiPost MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ApiPost MCP server in PolicyLayer and add a rule for apipost_create_folder: 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 ApiPost MCP. Nothing to install.
apipost_create_folder 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 apipost_create_folder 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 apipost_create_folder. 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.
apipost_create_folder is provided by the ApiPost MCP server (jlcodes99/apipost-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ApiPost MCP, 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.
6 ApiPost MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.