get_enabled

THE RISK

Low Risk

Why get_enabled needs a policy

This tool retrieves the current state of automation enablement. It performs no modifications, executions, or destructive operations. It is a straightforward read operation that queries system state, analogous to checking a flag or configuration value. The blast radius of misuse is minimal — an agent cannot cause harm by repeatedly checking this status.

From the tool's definition Tool name is 'get_enabled' and description states 'Check if automation is enabled' — a simple status query with no side effects.

Documented attack patterns abuse exactly the kind of access get_enabled gives an agent:

POLICY

How to control get_enabled

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 get_enabled:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_enabled": {}
  }
}

get_enabled is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register GNOME Desktop MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More GNOME Desktop MCP tools

Destructive cleanup_screenshots Remove all temporary screenshot files. Destructive close_window Close a window. Execute activate_workspace Switch to a workspace by index (0-based). Execute focus_window Focus and raise a window. Execute key_combo Press a key combination. Execute key_press Press and release a single key. Execute minimize_window Minimize a window. Execute mouse_click Click at screen coordinates. button: 1=left, 2=middle, 3=right.

All 30 GNOME Desktop MCP tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_enabled

What does the get_enabled tool do? +

Check if automation is enabled. It is categorised as a Read tool in the GNOME Desktop MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_enabled? +

Register the GNOME Desktop MCP server in PolicyLayer and add a rule for get_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.

What risk level is get_enabled? +

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

Can I rate-limit get_enabled? +

Yes. Add a rate_limit block to the get_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.

How do I block get_enabled completely? +

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

What MCP server provides get_enabled? +

get_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.

Enforce policy on every GNOME Desktop MCP tool call.

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.

CHECK YOUR STACK →