woo_system_status

Get system status information

SERVERCowork Bench SOURCE0717376/cowork_bench

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-bench/woo-system-status.md

WHAT IT DOES

What woo_system_status does on Cowork Bench

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

RISK

Why woo_system_status is rated Low

This tool retrieves system status data without modifying, executing, or deleting anything. It is a passive information retrieval operation, making it a Read category tool with low severity since system status information is typically non-sensitive operational metadata.

From the tool's definition Tool name 'woo_system_status' and description 'Get system status information' indicate a retrieval operation with no side effects. The verb 'Get' and the informational nature of 'system status' confirm read-only querying.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs woo_system_status safely

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

woo_system_status Allowed

woo_system_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": {
    "woo_system_status": {}
  }
}

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

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

FAQ

Questions about woo_system_status

What does the woo_system_status tool do? +

Get system status information. It is categorised as a Read tool in the Cowork Bench MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on woo_system_status? +

Register the Cowork Bench MCP server in PolicyLayer and add a rule for woo_system_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 Bench. Nothing to install.

What risk level is woo_system_status? +

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

Can I rate-limit woo_system_status? +

Yes. Add a rate_limit block to the woo_system_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 woo_system_status completely? +

Set action: deny in the PolicyLayer policy for woo_system_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 woo_system_status? +

woo_system_status is provided by the Cowork Bench MCP server (0717376/cowork_bench). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Cowork Bench, and thousands of servers like it.

This server

All 433 Cowork Bench 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 →