Low Risk

provider_subcommands_list

Return a compact, filterable read-only catalog of declared provider CLI subcommands without flags or raw help.

How to control provider_subcommands_list ↓

What provider_subcommands_list does on LLM CLI Gateway

AI agents call provider_subcommands_list to retrieve information from LLM CLI Gateway without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why provider_subcommands_list needs a policy

This tool queries and retrieves metadata about available CLI subcommands from multiple providers (Claude, Codex, Gemini, Grok, Mistral). It performs no modifications, deletions, or execution—it merely enumerates and filters existing command definitions. The blast radius if misused is minimal; an AI agent gaining access would only see what subcommands are available, not execute them or access sensitive data.

From the tool's definition Tool description states 'read-only catalog' and explicitly lists its purpose as returning declared subcommands 'without flags or raw help.' The word 'catalog' and 'read-only' confirm this is a retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access provider_subcommands_list gives an agent:

How to control provider_subcommands_list

PolicyLayer is an MCP gateway — it sits between your AI agents and LLM CLI Gateway, and nothing reaches the server without passing your rules. This is the rule we recommend for provider_subcommands_list:

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

provider_subcommands_list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register LLM CLI Gateway — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about provider_subcommands_list

What does the provider_subcommands_list tool do? +

Return a compact, filterable read-only catalog of declared provider CLI subcommands without flags or raw help. It is categorised as a Read tool in the LLM CLI Gateway MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on provider_subcommands_list? +

Register the LLM CLI Gateway MCP server in PolicyLayer and add a rule for provider_subcommands_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 LLM CLI Gateway. Nothing to install.

What risk level is provider_subcommands_list? +

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

Can I rate-limit provider_subcommands_list? +

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

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

provider_subcommands_list is provided by the LLM CLI Gateway MCP server (llm-cli-gateway). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every LLM CLI Gateway tool call.

Start from LLM CLI Gateway, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

46 LLM CLI Gateway tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.