update_chat_command · RunWhen Platform MCP: Risk & Policy

WHAT IT DOES

What update_chat_command does on RunWhen Platform MCP

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

WHY IT NEEDS A POLICY

Why update_chat_command needs a policy

The tool updates chat commands, which are configuration/metadata objects in the RunWhen workspace. This is a reversible modification (can be updated again or reverted), not deletion or financial transaction. However, confidence is moderate-to-high rather than very high because the description is empty, leaving some ambiguity about side effects.

From the tool's definition Tool name 'update_chat_command' indicates modification of chat command data within the RunWhen platform. The prefix 'update_' signals a Write operation that creates or modifies data reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_chat_command Rate-limited

update_chat_command 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": {
    "update_chat_command": {
      "limits": [
        {
          "counter": "update_chat_command_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches RunWhen Platform MCP, so you can run agents against it safely.

FAQ

Questions about update_chat_command

What does the update_chat_command tool do? +

update_chat_command. It is categorised as a Write tool in the RunWhen Platform MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_chat_command? +

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

What risk level is update_chat_command? +

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

Can I rate-limit update_chat_command? +

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

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

update_chat_command is provided by the RunWhen Platform MCP server (runwhen-contrib/runwhen-platform-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.