REST API, MCP server and CLI coverage
Every AbuseZero action, with its REST API endpoint, MCP server tool and CLI command.
The AbuseZero REST API, the AbuseZero MCP server and the AbuseZero CLI are three ways to reach the same AbuseZero actions, so an action takes the same input and returns the same result wherever you call it. The AbuseZero Node.js SDK covers every REST API endpoint, with a typed method or call().
Actions
Each REST API endpoint links to its reference section, each MCP tool to the MCP tools list and each command to the CLI command reference. Every action needs the same scope on every surface.
Connection actions
These manage the connection itself, so each one exists only where it applies.
| Action | AbuseZero MCP server | AbuseZero CLI |
|---|---|---|
| Sign in | Your app's sign-in flow, see MCP server authentication | abusezero login |
| Sign out | Your app's disconnect option | abusezero logout |
| Choose a workspace | abusezero_select_workspace | abusezero workspaces use |
| Show the connection | abusezero_get_connection_context | abusezero whoami |
| Run a local MCP server | None | abusezero mcp |
The MCP prompts review_policy, investigate_denial and simulate_policy_change are instructions for an AI app, so the CLI doesn't offer them.
Exclusions
Some capabilities are deliberately available on one surface only.
| Capability | Where it's available | Why |
|---|---|---|
| Browser observation | The AbuseZero browser SDK and standalone browser script, see Browser protection | Browser evidence must come from a real visitor's browser. A remote agent, a server or the CLI can't produce it. |
| Account security: password, two-step verification and linked sign-ins | Dashboard | These protect your own sign-in, so they always need you, signed in, in the dashboard. |
| API keys and machine clients | Dashboard, under Developers. See Keys and access | A credential can never create or widen another credential. |
| Billing, credits and plans | Dashboard, under Workspace settings → Billing & Subscriptions | Only the workspace owner manages billing. |
| Members, roles and ownership | Dashboard. See Workspaces | Changes to who can reach a workspace always need a signed-in person. |
| Workspace deletion | Dashboard | Deleting a workspace is permanent, so it always needs a signed-in person in the dashboard. |
How is this guide?
Last updated on