agentbrush_login
Authenticate this CLI with your AgentBrush account using device authorization. Opens a browser window where you approve the connection. After approval, API credentials are saved locally and persist across sessions. Only needs to be called once. Call this if agentbrush_check_status reports unauthe...
This record as markdown: /tools/dev-agentbrush-mcp-server/agentbrush-login.md
What agentbrush_login does on Mcp Server
AI agents use agentbrush_login to create or update resources in Mcp Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Server environment.
Why agentbrush_login is rated Medium
The tool authenticates the CLI and saves API credentials locally. This is a Write operation because it creates/stores persistent credentials on the local system. It's not purely Read (it has side effects) and not Execute (no code/commands run).
From the tool's definition API credentials are saved locally and persist across sessions
Attacks that exploit this kind of access
The rule that runs agentbrush_login safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For agentbrush_login, this is the rule to start with:
agentbrush_login 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 Mcp Server, apply this rule, and every agentbrush_login call is checked against it from then on.
Questions about agentbrush_login
Authenticate this CLI with your AgentBrush account using device authorization. Opens a browser window where you approve the connection. After approval, API credentials are saved locally and persist across sessions. Only needs to be called once. Call this if agentbrush_check_status reports unauthenticated, or if agentbrush_generate fails with an authentication error. If already authenticated with a valid key, returns the current plan and token balance without starting a new auth flow. The tool blocks while waiting for browser approval (up to 15 minutes). No input parameters required. It is categorised as a Write tool in the Mcp Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Server MCP server in PolicyLayer and add a rule for agentbrush_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 Mcp Server. Nothing to install.
agentbrush_login 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 agentbrush_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 agentbrush_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.
agentbrush_login is provided by the Mcp Server MCP server (@agentbrush/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Server, and thousands of servers like it.
This server
Across the catalogue