watch_room_todo

Subscribes a Chat room to one Jobs card. The scheduled room watcher posts a single line only when the card's material state changes.

SERVERUnClick SOURCE@unclick/mcp-server

Low RISK CLASS

Category Read

Parameters 22 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/watch-room-todo.md

WHAT IT DOES

What watch_room_todo does on UnClick

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

Parameter	Type	Required	Description
`todo_id`	string	Yes	Jobs card UUID.
`thread_id`	string	Yes	Chat thread UUID.

Parameters from the server's own tool schema.

RISK

Why watch_room_todo is rated Low

Even though watch_room_todo only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs watch_room_todo safely

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

watch_room_todo Allowed

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

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

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

FAQ

Questions about watch_room_todo

What does the watch_room_todo tool do? +

Subscribes a Chat room to one Jobs card. The scheduled room watcher posts a single line only when the card's material state changes. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.

What parameters does watch_room_todo accept? +

watch_room_todo accepts 2 parameters: todo_id, thread_id. Required: todo_id, thread_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on watch_room_todo? +

Register the UnClick MCP server in PolicyLayer and add a rule for watch_room_todo: 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 UnClick. Nothing to install.

What risk level is watch_room_todo? +

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

Can I rate-limit watch_room_todo? +

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

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

watch_room_todo is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on UnClick, and thousands of servers like it.

This server

All 1662 UnClick tools →

Across the catalogue

The MCP Attack Database →

Guides

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