happ_assistant_transfer
Переносит ассистента в другую компанию — копия в целевой компании + безопасное удаление исходного. (POST /assistants-new/:id/company/:companyId)
This record as markdown: /tools/happ-ai-platform-mcp/happ-assistant-transfer.md
What happ_assistant_transfer does on Platform
AI agents use happ_assistant_transfer to commit financial operations through Platform, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
assistantId | string | Yes | ID ассистента |
targetCompanyId | string | Yes | ID компании-получателя |
Parameters from the server's own tool schema.
Why happ_assistant_transfer is rated Critical
happ_assistant_transfer moves real money, and an autonomous agent will call it with the same confidence it calls a search tool. A misread instruction or an injected prompt is all it takes to drain an account or blow a budget.
Attacks that exploit this kind of access
The rule that runs happ_assistant_transfer 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_assistant_transfer, this is the rule to start with:
Any call to happ_assistant_transfer is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Platform, apply this rule, and every happ_assistant_transfer call is checked against it from then on.
Questions about happ_assistant_transfer
Переносит ассистента в другую компанию — копия в целевой компании + безопасное удаление исходного. (POST /assistants-new/:id/company/:companyId). It is categorised as a Financial tool in the Platform MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
happ_assistant_transfer accepts 2 parameters: assistantId, targetCompanyId. Required: assistantId, targetCompanyId. 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_assistant_transfer: 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_assistant_transfer is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the happ_assistant_transfer 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_assistant_transfer. 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_assistant_transfer 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.
Across the catalogue