extension_atlas_list

Enumerate user-local overlay namespaces and their entity_type counts.

SERVERLivepilot SOURCElivepilot

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-dreamrec-livepilot/extension-atlas-list.md

WHAT IT DOES

What extension_atlas_list does on Livepilot

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

RISK

Why extension_atlas_list is rated Low

The tool performs enumeration and counting of existing entities, which is a read-only data retrieval operation. There are no side effects, no data modification, no code execution, and no destructive actions. The blast radius of misuse is minimal — an AI agent could only gain visibility into namespace structure, not affect the system or user's music project.

From the tool's definition Tool description states 'Enumerate user-local overlay namespaces and their entity_type counts' — this is a listing/query operation that retrieves metadata about existing namespaces without modifying or executing anything.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs extension_atlas_list safely

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

extension_atlas_list Allowed

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

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

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

FAQ

Questions about extension_atlas_list

What does the extension_atlas_list tool do? +

Enumerate user-local overlay namespaces and their entity_type counts. It is categorised as a Read tool in the Livepilot MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on extension_atlas_list? +

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

What risk level is extension_atlas_list? +

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

Can I rate-limit extension_atlas_list? +

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

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

extension_atlas_list is provided by the Livepilot MCP server (livepilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Livepilot, and thousands of servers like it.

This server

All 474 Livepilot 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 →