Authenticate with tru via the browser. Opens a browser window where the user selects their account and verifies their identity, then waits until authentication is complete. Credentials are stored locally for future sessions. Set switch_account to true to log out and re-authenticate as a different...
AI agents invoke login to trigger actions in Tru. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
switch_account | boolean | — | Log out first and authenticate as a different user |
Parameters from the server's own tool schema.
This tool triggers an external browser-based authentication flow and persists credentials locally — it executes an external operation with side effects (storing credentials, establishing a session). It does not merely read data, and while it writes credentials locally, the primary action is launching and coordinating an external browser operation, making Execute the most accurate category.
From the tool's definition Opens a browser window where the user selects their account and verifies their identity, then waits until authentication is complete. Credentials are stored locally for future sessions.
Attacks that exploit this kind of access
Authenticate with tru via the browser. Opens a browser window where the user selects their account and verifies their identity, then waits until authentication is complete. Credentials are stored locally for future sessions. Set switch_account to true to log out and re-authenticate as a different user. Before calling this tool, tell the user: 'Opening your browser to verify your identity with tru — complete the login there and I\'ll continue automatically.'. It is categorised as a Execute tool in the Tru MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
login accepts 1 parameter: switch_account. The full parameter table on this page comes from the server's own tool schema.
Register the Tru MCP server in PolicyLayer and add a rule for 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 Tru. Nothing to install.
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 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 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.
login is provided by the Tru MCP server (tru-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 →