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 ...
This record as markdown: /tools/dev-agentbrush-mcp-server/agentbrush-check-status.md
What agentbrush_check_status does on Mcp Server
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.
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 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.
Attacks that exploit this kind of access
The rule that runs agentbrush_check_status 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_check_status, this is the rule to start with:
agentbrush_check_status is read-only, so it stays allowed. 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_check_status call is checked against it from then on.
Questions about 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). It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.
Register the Mcp Server MCP server in PolicyLayer and add a rule for agentbrush_check_status: 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_check_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the agentbrush_check_status 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_check_status. 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_check_status 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