get_config
Get the complete server configuration as JSON. Config includes fields for: - blockedCommands (array of blocked shell commands) - defaultShell (shell to use for commands) - allowedDirectories (paths the server can access) - fileReadLineLimit (max lines for read_file, default 1000) - fileWriteLineL...
This record as markdown: /tools/desktop-commander/get-config.md
What get_config does on Desktop Commander
AI agents call get_config 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.
Why get_config is rated Low
This is a Read operation as it only retrieves and queries existing configuration data without side effects. However, severity is high because the configuration includes sensitive security settings (blocked commands, allowed directories, rate limits) that could be exploited by an attacker to understand and bypass server restrictions.
From the tool's definition Tool name 'get_config' and description 'Get the complete server configuration as JSON' indicate retrieval of configuration data without modification.
Attacks that exploit this kind of access
The rule that runs get_config 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 get_config, this is the rule to start with:
get_config is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Desktop Commander, apply this rule, and every get_config call is checked against it from then on.
Questions about get_config
Get the complete server configuration as JSON. Config includes fields for: - blockedCommands (array of blocked shell commands) - defaultShell (shell to use for commands) - allowedDirectories (paths the server can access) - fileReadLineLimit (max lines for read_file, default 1000) - fileWriteLineLimit (max lines per write_file call, default 50) - telemetryEnabled (boolean for telemetry opt-in/out) - currentClient (information about the currently connected MCP client) - clientHistory (history of all clients that have connected) - version (version of the DesktopCommander) - systemInfo (operating system and environment details) ${CMD_PREFIX_DESCRIPTION}. It is categorised as a Read tool in the Desktop Commander MCP Server, which means it retrieves data without modifying state.
Register the Desktop Commander MCP server in PolicyLayer and add a rule for get_config: 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.
get_config is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_config 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.
Set action: deny in the PolicyLayer policy for get_config. 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.
get_config 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.
More on Desktop Commander, and thousands of servers like it.
This server
Across the catalogue