Remove a command from the blacklist. Once unblocked, the command can be executed normally.
AI agents invoke unblock_command to trigger actions in Desktop Commander MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Unblocking a command modifies the security policy of the MCP server, enabling previously restricted commands to be executed. This is a security-control bypass that enables execution of arbitrary commands. While it modifies a configuration (Write), the primary risk and purpose is enabling execution of blocked commands, making Execute the most appropriate and severe category.
From the tool's definition "Remove a command from the blacklist. Once unblocked, the command can be executed normally."
Documented attack patterns abuse exactly the kind of access unblock_command gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Desktop Commander MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for unblock_command:
{
"version": "1",
"default": "deny",
"tools": {
"unblock_command": {
"limits": [
{
"counter": "unblock_command_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}unblock_command stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Remove a command from the blacklist. Once unblocked, the command can be executed normally. It is categorised as a Execute tool in the Desktop Commander MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Desktop Commander MCP server in PolicyLayer and add a rule for unblock_command: 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. Nothing to install.
unblock_command is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the unblock_command 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 unblock_command. 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.
unblock_command is provided by the Desktop Commander MCP server (mrgnss/claudedesktopcommander). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from 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 Desktop Commander MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.