app_list

List installed .0n applications from ~/.0n/apps/. Example: app_list({})

SERVER0nmcp SOURCE0nmcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-0nork-0nmcp/app-list.md

WHAT IT DOES

What app_list does on 0nmcp

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

RISK

Why app_list is rated Low

This tool retrieves information about installed applications from a local filesystem directory. It performs a query/list operation that does not modify, execute, or delete anything. The action is purely informational and has no external effects beyond returning data to the caller.

From the tool's definition Tool name is 'app_list' and description states it 'List[s] installed .0n applications from ~/.0n/apps/'. The verb 'list' and the read-only nature of querying a local directory for installed applications indicate data retrieval with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs app_list safely

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

app_list Allowed

app_list 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": {
    "app_list": {}
  }
}

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

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

FAQ

Questions about app_list

What does the app_list tool do? +

List installed .0n applications from ~/.0n/apps/. Example: app_list({}). It is categorised as a Read tool in the 0nmcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on app_list? +

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

What risk level is app_list? +

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

Can I rate-limit app_list? +

Yes. Add a rate_limit block to the app_list 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 app_list completely? +

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

app_list is provided by the 0n MCP server (0nmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on 0n, and thousands of servers like it.

This server

All 218 0n tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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