infra_status

Get overall infrastructure status: provider connections, active sandboxes, wallet state.

SERVERCoWork OS SOURCECoWork-OS/CoWork-OS

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cowork-os/infra-status.md

WHAT IT DOES

What infra_status does on CoWork OS

AI agents call infra_status to retrieve information from CoWork OS without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why infra_status is rated Low

This tool performs information retrieval with no side effects. It reads current infrastructure status and wallet state without modifying, executing, or destroying anything. While it accesses wallet state information, it does not move money or commit financial obligations—it merely reports the wallet state, making it a Read operation.

From the tool's definition The tool 'infra_status' retrieves status information ('Get overall infrastructure status') about provider connections, active sandboxes, and wallet state. It queries existing state without creating, modifying, deleting, or executing operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs infra_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For infra_status, this is the rule to start with:

infra_status Allowed

infra_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "infra_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect CoWork OS, apply this rule, and every infra_status call is checked against it from then on.

FAQ

Questions about infra_status

What does the infra_status tool do? +

Get overall infrastructure status: provider connections, active sandboxes, wallet state. It is categorised as a Read tool in the CoWork OS MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on infra_status? +

Register the CoWork OS MCP server in PolicyLayer and add a rule for infra_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 CoWork OS. Nothing to install.

What risk level is infra_status? +

infra_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit infra_status? +

Yes. Add a rate_limit block to the infra_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.

How do I block infra_status completely? +

Set action: deny in the PolicyLayer policy for infra_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.

What MCP server provides infra_status? +

infra_status is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CoWork OS, and thousands of servers like it.

This server

All 342 CoWork OS tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →