happ_playground_send
Отправляет сообщение в playground-чат от имени клиента и ЖДЁТ ответ ассистента (до ~30 с) — возвращает его в поле reply. Так проверяют, как ассистент отвечает: приветствие, реакцию на вопрос, соблюдение промпта. Если reply=null — ответ не успел прийти, повтори happ_chat_messages по чату чуть позж...
This record as markdown: /tools/happ-ai-platform-mcp/happ-playground-send.md
What happ_playground_send does on Platform
AI agents use happ_playground_send to create or update resources in Platform, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Platform environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
text | string | Yes | Текст сообщения |
chatId | string | Yes | ID playground-чата |
Parameters from the server's own tool schema.
Why happ_playground_send is rated Medium
An AI agent can call happ_playground_send faster than any human can review: one bad instruction and it creates or modifies resources in Platform by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs happ_playground_send safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Platform, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For happ_playground_send, this is the rule to start with:
happ_playground_send 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Platform, apply this rule, and every happ_playground_send call is checked against it from then on.
Questions about happ_playground_send
Отправляет сообщение в playground-чат от имени клиента и ЖДЁТ ответ ассистента (до ~30 с) — возвращает его в поле reply. Так проверяют, как ассистент отвечает: приветствие, реакцию на вопрос, соблюдение промпта. Если reply=null — ответ не успел прийти, повтори happ_chat_messages по чату чуть позже. (POST /chats/playground/:id/messages; GET /messages?chatId=…). It is categorised as a Write tool in the Platform MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
happ_playground_send accepts 2 parameters: text, chatId. Required: text, chatId. The full parameter table on this page comes from the server's own tool schema.
Register the Platform MCP server in PolicyLayer and add a rule for happ_playground_send: 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 Platform. Nothing to install.
happ_playground_send 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 happ_playground_send 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 happ_playground_send. 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.
happ_playground_send is provided by the Platform MCP server (@happ-ai/platform-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Platform, and thousands of servers like it.
This server
Across the catalogue