Health check for the current workspace (auth state, tier, gating, blockers).
AI agents call check_workspace_status to retrieve information from APIClaw without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries workspace configuration and auth state data without modifying anything, making it a Read operation. However, severity is high because the returned information (auth state, tier, gating rules, blockers) is sensitive and could inform attackers about access control, restrictions, or vulnerabilities in the workspace setup.
From the tool's definition 'Health check for the current workspace (auth state, tier, gating, blockers)' retrieves sensitive workspace metadata including authentication state, service tier, access gating settings, and operational blockers.
Documented attack patterns abuse exactly the kind of access check_workspace_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and APIClaw, and nothing reaches the server without passing your rules. This is the rule we recommend for check_workspace_status:
{
"version": "1",
"default": "deny",
"tools": {
"check_workspace_status": {}
}
}check_workspace_status 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.
Health check for the current workspace (auth state, tier, gating, blockers). It is categorised as a Read tool in the APIClaw MCP Server, which means it retrieves data without modifying state.
Register the APIClaw MCP server in PolicyLayer and add a rule for check_workspace_status: 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 APIClaw. Nothing to install.
check_workspace_status 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 check_workspace_status 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 check_workspace_status. 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.
check_workspace_status is provided by the APIClaw MCP server (nordsym/apiclaw). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from APIClaw, 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.
24 APIClaw tools catalogued and risk-classified — across an index of 43,000+ MCP servers.