AI agents call apipost_workspace 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 only retrieves information about workspaces, teams, and projects, and switches between workspaces. These are all read operations or benign navigation changes with no side effects on data. No creation, modification, deletion, or execution of external operations occurs.
From the tool's definition Tool description states '查看当前工作空间' (view current workspace) and '列出团队和项目' (list teams and projects), which are read operations. The action '切换工作空间' (switch workspace) is a navigation/state change with no data modification or deletion.
Documented attack patterns abuse exactly the kind of access apipost_workspace 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_workspace:
{
"version": "1",
"default": "deny",
"tools": {
"apipost_workspace": {}
}
}apipost_workspace 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.
工作空间管理：查看当前工作空间、列出团队和项目、切换工作空间. 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_workspace: 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_workspace 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_workspace 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_workspace. 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_workspace 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.