Low Risk

list_blocked_commands

List all currently blocked commands.

How to control list_blocked_commands ↓

What list_blocked_commands does on Claude Desktop Commander MCP

AI agents call list_blocked_commands to retrieve information from Claude Desktop Commander MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why list_blocked_commands needs a policy

This tool only retrieves and displays information about blocked commands. It performs a read-only query of existing configuration state without creating, modifying, executing, deleting, or moving any data or processes. The low severity reflects that misuse poses minimal risk—an AI agent listing blocked commands cannot harm the system.

From the tool's definition Tool name is 'list_blocked_commands' and description states 'List all currently blocked commands' — a pure query/retrieval operation with no side effects.

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

How to control list_blocked_commands

PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Desktop Commander MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for list_blocked_commands:

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

list_blocked_commands 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 Claude Desktop Commander MCP — 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 list_blocked_commands

What does the list_blocked_commands tool do? +

List all currently blocked commands. It is categorised as a Read tool in the Claude Desktop Commander MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_blocked_commands? +

Register the Claude Desktop Commander MCP server in PolicyLayer and add a rule for list_blocked_commands: 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 Claude Desktop Commander MCP. Nothing to install.

What risk level is list_blocked_commands? +

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

Can I rate-limit list_blocked_commands? +

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

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

list_blocked_commands is provided by the Claude Desktop Commander MCP server (strawhatai/claude-dev-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Claude Desktop Commander MCP tool call.

Start from Claude Desktop Commander MCP, 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.

19 Claude Desktop Commander MCP 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.