# agentbrush_check_status

Check AgentBrush authentication status, plan details, and token balance. Returns: authentication state, plan name, token balance, monthly allocation, cycle reset date, and quota state. Requires authentication (credentials must exist from a prior agentbrush_login). If not authenticated, returns a suggestion to run agentbrush_login. Call this before agentbrush_generate if you need to confirm the user has enough tokens for a generation. The response includes a human-readable summary you can relay directly to the user, including how many generations they can afford. Handles gracefully: missing credentials (suggests login), API unreachable (suggests retry), expired/revoked keys (suggests re-login).

Agent View of the PolicyLayer registry record for `agentbrush_check_status`. HTML page: https://policylayer.com/tools/dev-agentbrush-mcp-server/agentbrush-check-status

## Facts

- Tool: `agentbrush_check_status`
- Server: Mcp Server (`@agentbrush/mcp-server`) — https://policylayer.com/tools/dev-agentbrush-mcp-server.md
- Install: `npx -y @agentbrush/mcp-server`
- Homepage: https://www.npmjs.com/package/@agentbrush/mcp-server
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "agentbrush_check_status",
    "arguments": {}
  }
}
```

## Why agentbrush_check_status is rated Low

This tool retrieves and queries account status information (authentication state, plan details, token balance, quotas) without modifying any data or triggering side effects. It is purely informational and read-only. The use case of checking token balance before generation is a typical pre-flight check.

From the tool's own definition: "Check AgentBrush authentication status, plan details, and token balance. Returns: authentication state, plan name, token balance, monthly allocation, cycle reset date, and quota state."

## Use case

AI agents call agentbrush_check_status to retrieve information from Mcp Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Mcp Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "agentbrush_check_status": {}
  }
}
```

## Other tools on Mcp Server (11)

- `agentbrush_remove_background` — Destructive — https://policylayer.com/tools/dev-agentbrush-mcp-server/agentbrush-remove-background.md
- `agentbrush_edit_mask` — Execute — https://policylayer.com/tools/dev-agentbrush-mcp-server/agentbrush-edit-mask.md
- `agentbrush_edit_mask_open` — Execute — https://policylayer.com/tools/dev-agentbrush-mcp-server/agentbrush-edit-mask-open.md
- `agentbrush_list_presets` — Read — https://policylayer.com/tools/dev-agentbrush-mcp-server/agentbrush-list-presets.md
- `agentbrush_list_references` — Read — https://policylayer.com/tools/dev-agentbrush-mcp-server/agentbrush-list-references.md
- `agentbrush_edit_mask_result` — Write — https://policylayer.com/tools/dev-agentbrush-mcp-server/agentbrush-edit-mask-result.md
- `agentbrush_generate` — Write — https://policylayer.com/tools/dev-agentbrush-mcp-server/agentbrush-generate.md
- `agentbrush_init` — Write — https://policylayer.com/tools/dev-agentbrush-mcp-server/agentbrush-init.md
- `agentbrush_login` — Write — https://policylayer.com/tools/dev-agentbrush-mcp-server/agentbrush-login.md
- `agentbrush_populate_identity` — Write — https://policylayer.com/tools/dev-agentbrush-mcp-server/agentbrush-populate-identity.md
- `agentbrush_save_as_reference` — Write — https://policylayer.com/tools/dev-agentbrush-mcp-server/agentbrush-save-as-reference.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=dev-agentbrush-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/dev-agentbrush-mcp-server