wayland_info

THE RISK

Low Risk

Why wayland_info needs a policy

This tool simply lists or queries the state of Wayland protocols in the session. It has no side effects, does not modify state, does not execute commands, and does not delete or move resources. It is purely informational, matching the 'Read' category definition of retrieving or querying data with no side effects.

From the tool's definition Tool name 'wayland_info' and description 'List Wayland protocols available in the isolated session' indicate a query/enumeration operation that retrieves information about available protocols without modifying or executing anything.

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

POLICY

How to control wayland_info

PolicyLayer is an MCP gateway — it sits between your AI agents and Kwin, and nothing reaches the server without passing your rules. This is the rule we recommend for wayland_info:

policy.json

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

wayland_info 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 Kwin — 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 Kwin tools

Execute launch_app launch_app Execute session_start session_start Execute session_stop session_stop Execute wait_for_element wait_for_element Execute dbus_call dbus_call Execute focus_window Attempt to focus a window by application name. Execute keyboard_key keyboard_key Execute keyboard_key_down Press and hold a key without releasing.

All 30 Kwin 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 wayland_info

What does the wayland_info tool do? +

List Wayland protocols available in the isolated session. It is categorised as a Read tool in the Kwin MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on wayland_info? +

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

What risk level is wayland_info? +

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

Can I rate-limit wayland_info? +

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

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

wayland_info is provided by the Kwin MCP server (isac322/kwin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Kwin tool call.

Start from Kwin, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →