AI agents call apipost_list to retrieve information from ApiPost MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists API documentation from ApiPost projects. It performs a read-only query operation with no side effects—it searches and displays existing data without creating, modifying, or deleting anything. The sibling tools 'apipost_create_folder', 'apipost_delete', and 'apipost_test_connection' are separate actions; this one is purely for listing/viewing.
From the tool's definition Tool name 'apipost_list' and description '查看项目API列表' (view project API list) indicates data retrieval. The phrase '支持强化的目录层级搜索' (supports enhanced directory hierarchy search) confirms query/search functionality without modification.
Documented attack patterns abuse exactly the kind of access apipost_list 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_list:
{
"version": "1",
"default": "deny",
"tools": {
"apipost_list": {}
}
}apipost_list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
查看项目API列表，支持强化的目录层级搜索和父子关系定位. It is categorised as a Read tool in the ApiPost MCP MCP Server, which means it retrieves data without modifying state.
Register the ApiPost MCP server in PolicyLayer and add a rule for apipost_list: 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_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the apipost_list 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_list. 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_list 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.