do_account

Get the DigitalOcean account profile and limits.

SERVERUnClick SOURCE@unclick/mcp-server

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/do-account.md

WHAT IT DOES

What do_account does on UnClick

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

Parameter	Type	Required	Description
`access_token`	string	Yes	DigitalOcean personal access token

Parameters from the server's own tool schema.

RISK

Why do_account is rated Low

This tool retrieves account information from DigitalOcean, which is a read-only operation with no side effects. It does not create, modify, delete, execute commands, or commit financial transactions. The blast radius is limited to information disclosure of the account holder's profile details and service limits.

From the tool's definition The tool name 'do_account' and description 'Get the DigitalOcean account profile and limits' clearly indicate a retrieval operation.

Risk signalsHandles credentials or secrets (access_token)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs do_account safely

PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For do_account, this is the rule to start with:

do_account Allowed

do_account is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "do_account": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every do_account call is checked against it from then on.

FAQ

Questions about do_account

What does the do_account tool do? +

Get the DigitalOcean account profile and limits. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.

What parameters does do_account accept? +

do_account accepts 1 parameter: access_token. Required: access_token. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on do_account? +

Register the UnClick MCP server in PolicyLayer and add a rule for do_account: 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 UnClick. Nothing to install.

What risk level is do_account? +

do_account is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit do_account? +

Yes. Add a rate_limit block to the do_account 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.

How do I block do_account completely? +

Set action: deny in the PolicyLayer policy for do_account. 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.

What MCP server provides do_account? +

do_account is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on UnClick, and thousands of servers like it.

This server

All 1662 UnClick tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →