AI agents invoke set_enabled to trigger actions in GNOME Desktop 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.
This tool acts as a master switch for desktop automation capabilities including mouse/keyboard injection, window management, and other GNOME desktop controls. Disabling it could disrupt ongoing AI agent operations or lock out automation entirely; enabling it activates a broad suite of high-privilege desktop control tools. The blast radius is high because it gates access to all 30 automation tools on the server.
From the tool's definition 'Enable or disable automation' — controls whether the automation system is active
Documented attack patterns abuse exactly the kind of access set_enabled gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GNOME Desktop MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for set_enabled:
{
"version": "1",
"default": "deny",
"tools": {
"set_enabled": {
"limits": [
{
"counter": "set_enabled_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}set_enabled 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.
Enable or disable automation. It is categorised as a Execute tool in the GNOME Desktop MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the GNOME Desktop MCP server in PolicyLayer and add a rule for set_enabled: 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 GNOME Desktop MCP. Nothing to install.
set_enabled 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 set_enabled 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 set_enabled. 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.
set_enabled is provided by the GNOME Desktop MCP server (sbuysse/gnome-desktop-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from GNOME Desktop 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.
30 GNOME Desktop MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.