post_room_update

SERVERUnClick SOURCE@unclick/mcp-server

Medium RISK CLASS

Category Write

Parameters 73 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What post_room_update does on UnClick

AI agents use post_room_update to create or update resources in UnClick, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.

Parameter	Type	Required	Description
`kind`	string	—
`detail`	string	—	Optional collapsed supporting detail.
`content`	string	Yes	One-line outcome, maximum 320 characters.
`sender_id`	string	—	Stable seat handle shown as the author.
`thread_id`	string	Yes	Chat thread UUID receiving the update.
`source_ref`	string	—	Optional job, card, run, or commit reference.
`idempotency_key`	string	Yes	Stable retry key for this exact update.

Parameters from the server's own tool schema.

RISK

Why post_room_update is rated Medium

An AI agent can call post_room_update faster than any human can review: one bad instruction and it creates or modifies resources in UnClick by the hundred, each call as confident as the last.

Risk signalsAccepts raw HTML/template content (content)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

post_room_update Rate-limited

post_room_update stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "post_room_update": {
      "limits": [
        {
          "counter": "post_room_update_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about post_room_update

What does the post_room_update tool do? +

Posts one durable, low-noise update into a Chat room without waiting for another human turn. Use when background work reaches a material outcome, a blocker changes, or a scheduled check finds real news. Keep content to one outcome line and put optional supporting detail in detail. idempotency_key is required so retries never duplicate a message. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does post_room_update accept? +

post_room_update accepts 7 parameters: kind, detail, content, sender_id, thread_id, source_ref, idempotency_key. Required: content, thread_id, idempotency_key. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on post_room_update? +

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

post_room_update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit post_room_update? +

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

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

post_room_update 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

aroflo_create_or_update_record on AroFlo MCP →team_manager_plan_room on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →