create_chat_command
AI agents use create_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.
The tool creates (write operation) a new chat command, modifying the workspace state reversibly. Without a description, confidence is reduced. This is categorized as Write rather than Execute because 'create' operations typically define or register commands rather than immediately execute them.
From the tool's definition Tool name 'create_chat_command' indicates creation of a new chat command resource. Sibling tools show patterns of workspace management (create_assistant, create_knowledge_base_article, etc.), suggesting this creates a new chat command object within the…
Attacks that exploit this kind of access
create_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.
Register the RunWhen Platform MCP server in PolicyLayer and add a rule for create_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.
create_chat_command is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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.
Set action: deny in the PolicyLayer policy for create_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.
create_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →