happ_login
Авторизация на платформе Happ через браузер. Открывает страницу входа, ждёт подтверждения пользователя и сохраняет токены локально. Вызывай ТОЛЬКО когда пользователь явно попросил залогиниться или подтвердил повторный вход. Никогда не вызывай автоматически в ответ на 401/'Не выполнен вход' — инст...
This record as markdown: /tools/happ-ai-platform-mcp/happ-login.md
What happ_login does on Platform
AI agents invoke happ_login to trigger actions in Platform. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why happ_login is rated High
This tool triggers external operations: it opens a browser window on the user's machine, waits for user interaction, and then saves authentication tokens locally. This constitutes executing a browser action with significant side effects (credential storage, browser window opening), placing it in the Execute category.
From the tool's definition Открывает страницу входа, ждёт подтверждения пользователя и сохраняет токены локально. Никогда не вызывай автоматически — инструмент открывает окно браузера у пользователя.
Attacks that exploit this kind of access
The rule that runs happ_login 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_login, this is the rule to start with:
happ_login stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_login call is checked against it from then on.
Questions about happ_login
Авторизация на платформе Happ через браузер. Открывает страницу входа, ждёт подтверждения пользователя и сохраняет токены локально. Вызывай ТОЛЬКО когда пользователь явно попросил залогиниться или подтвердил повторный вход. Никогда не вызывай автоматически в ответ на 401/'Не выполнен вход' — инструмент открывает окно браузера у пользователя. It is categorised as a Execute tool in the Platform MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Platform MCP server in PolicyLayer and add a rule for happ_login: 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_login is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the happ_login 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_login. 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_login 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