Low Risk

list_extensions

List extensions under an app with status, version, and bundle URL. Requires CLI auth.

Part of the Mcp App Extension server.

list_extensions is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE MCP APP EXTENSION →

Free to start. No card required.

AI agents call list_extensions to retrieve information from Mcp App Extension without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though list_extensions only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_extensions": {}
  }
}

See the full Mcp App Extension policy for all 8 tools.

Get this rule live on your own Mcp App Extension server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY MCP APP EXTENSION →

These attack patterns abuse exactly the kind of access list_extensions gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so list_extensions only ever does what you allow.

SECURE MCP APP EXTENSION →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the list_extensions tool do? +

List extensions under an app with status, version, and bundle URL. Requires CLI auth.. It is categorised as a Read tool in the Mcp App Extension MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_extensions? +

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

What risk level is list_extensions? +

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

Can I rate-limit list_extensions? +

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

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

list_extensions is provided by the Mcp App Extension MCP server (@stackable-labs/mcp-app-extension). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp App Extension tool call.

Deterministic rules across all 8 Mcp App Extension tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.