This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/do-list-apps.md
What do_list_apps does on UnClick
AI agents call do_list_apps 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 |
|---|---|---|---|
limit | number | — | Apps to return (max 200, default 25) |
access_token | string | Yes | DigitalOcean personal access token |
Parameters from the server's own tool schema.
Why do_list_apps is rated Low
This tool performs a data retrieval operation ('List') that enumerates DigitalOcean App Platform applications. It has no side effects, does not modify or delete data, and does not execute code or trigger external operations. The blast radius of misuse is minimal—an attacker could enumerate deployed apps but cannot modify, delete, or interact with them through this tool alone.
From the tool's definition Tool name 'do_list_apps' and description 'List DigitalOcean App Platform apps' indicate a read-only operation that retrieves and displays existing application information without modification.
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
The rule that runs do_list_apps 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_list_apps, this is the rule to start with:
do_list_apps 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 UnClick, apply this rule, and every do_list_apps call is checked against it from then on.
Questions about do_list_apps
List DigitalOcean App Platform apps. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
do_list_apps accepts 2 parameters: limit, access_token. Required: access_token. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for do_list_apps: 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.
do_list_apps 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 do_list_apps 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 do_list_apps. 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.
do_list_apps 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.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue