Low Risk

get_device_capabilities

Resolve one device and return its standard capability schema for stable client-side routing.

How to control get_device_capabilities ↓

What get_device_capabilities does on 米家 MCP Server

AI agents call get_device_capabilities to retrieve information from 米家 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_device_capabilities needs a policy

This tool retrieves capability information about a smart home device to enable client-side routing decisions. It performs a read-only query without creating, modifying, deleting, or executing any actions on devices or smart home systems. The capability schema is informational metadata used for UI/routing logic, not for control or state changes.

From the tool's definition Tool description states it 'Resolve one device and return its standard capability schema' - a retrieval operation with no modification or side effects. The verb 'return' and noun 'schema' indicate data querying.

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

How to control get_device_capabilities

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_device_capabilities": {}
  }
}

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

  1. Create a free account and register 米家 MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_device_capabilities

What does the get_device_capabilities tool do? +

Resolve one device and return its standard capability schema for stable client-side routing. It is categorised as a Read tool in the 米家 MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_device_capabilities? +

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

What risk level is get_device_capabilities? +

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

Can I rate-limit get_device_capabilities? +

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

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

get_device_capabilities is provided by the 米家 MCP Server MCP server (javen-yan/miot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every 米家 MCP Server tool call.

Start from 米家 MCP Server, 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.

26 米家 MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.