search_installed_apps

A read tool on the Desktop Commander MCP server.

SERVERDesktop Commander MCP Server SOURCE19miha99/system-monitor-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/19miha99-system-monitor-mcp/search-installed-apps.md

WHAT IT DOES

What search_installed_apps does on Desktop Commander MCP Server

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

RISK

Why search_installed_apps is rated Low

Based on the tool name and the pattern of sibling tools on this server, 'search_installed_apps' most likely performs a query or enumeration of installed applications without modifying system state. This is a Read operation.

From the tool's definition Tool name 'search_installed_apps' indicates querying/listing installed applications. No description provided, but naming convention suggests a read-only lookup operation consistent with sibling tools like 'find_process_by_port', 'get_process_details', and…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs search_installed_apps safely

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

search_installed_apps Allowed

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

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

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

FAQ

Questions about search_installed_apps

What does the search_installed_apps tool do? +

search_installed_apps is a read tool on the Desktop Commander MCP Server MCP server. It is categorised as a Read tool in the Desktop Commander MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_installed_apps? +

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

What risk level is search_installed_apps? +

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

Can I rate-limit search_installed_apps? +

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

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

search_installed_apps is provided by the Desktop Commander MCP Server MCP server (19miha99/system-monitor-mcp). 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 MCP Server, and thousands of servers like it.

This server

All 23 Desktop Commander MCP Server tools →

Across the catalogue

binary_search on 010 Editor →evaluate_search_quality on ACE-MCP →search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server → The MCP Attack Database →

Guides

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