list_searches

SERVERDesktop Commander SOURCEwonderwhy-er/DesktopCommanderMCP

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/desktop-commander/list-searches.md

WHAT IT DOES

What list_searches does on Desktop Commander

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

RISK

Why list_searches is rated Low

The tool retrieves and displays information about active searches without modifying, deleting, or executing any operations. It is purely informational, similar to a 'list' or 'get' operation. The severity is low because reading search metadata poses minimal risk even if misused by an AI agent.

From the tool's definition Tool name is 'list_searches' and description states it 'Shows search IDs, search types, patterns, status, and runtime' and is 'Useful for managing multiple concurrent searches.' This is a query/list operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_searches safely

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

list_searches Allowed

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

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

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

FAQ

Questions about list_searches

What does the list_searches tool do? +

List all active searches. Shows search IDs, search types, patterns, status, and runtime. Similar to list_sessions for terminal processes. Useful for managing multiple concurrent searches. ${CMD_PREFIX_DESCRIPTION}. It is categorised as a Read tool in the Desktop Commander MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_searches? +

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

What risk level is list_searches? +

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

Can I rate-limit list_searches? +

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

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

list_searches is provided by the Desktop Commander MCP server (wonderwhy-er/DesktopCommanderMCP). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Desktop Commander, and thousands of servers like it.

This server

All 11 Desktop Commander tools →

Across the catalogue

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

Guides

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