demo_read

Demo read tool

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/demo-read.md

WHAT IT DOES

What demo_read does on CoWork OS

AI agents call demo_read 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 demo_read is rated Low

The tool is explicitly named 'demo_read' and described as a 'Demo read tool', which clearly signals a read-only operation. As a demonstration tool, it is intended for querying or retrieving information without modifying, executing, or destroying data. The severity is low because even if misused, a read operation has no destructive or harmful side effects on the system.

From the tool's definition Tool name 'demo_read' and description 'Demo read tool' indicate a demonstration tool designed for reading/retrieving data with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs demo_read 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 demo_read, this is the rule to start with:

demo_read Allowed

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

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 demo_read call is checked against it from then on.

FAQ

Questions about demo_read

What does the demo_read tool do? +

Demo read tool. 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 demo_read? +

Register the CoWork OS MCP server in PolicyLayer and add a rule for demo_read: 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 demo_read? +

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

Can I rate-limit demo_read? +

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

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

demo_read 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_read_file on Claude Bridge → The MCP Attack Database →

Guides

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