Low Risk

get_service_status

Return service status, authentication status, and local file locations.

How to control get_service_status ↓

What get_service_status does on 米家 MCP Server

AI agents call get_service_status 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_service_status needs a policy

This tool queries and retrieves status information about the service, authentication state, and file system paths. It performs read-only operations without creating, modifying, deleting, or executing external actions. The information returned (status, authentication state, file paths) are metadata queries with no blast radius if misused by an AI agent.

From the tool's definition Tool name 'get_service_status' and description 'Return service status, authentication status, and local file locations' indicate data retrieval with no modification or side effects.

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

How to control get_service_status

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

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

get_service_status 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_service_status

What does the get_service_status tool do? +

Return service status, authentication status, and local file locations. 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_service_status? +

Register the 米家 MCP Server MCP server in PolicyLayer and add a rule for get_service_status: 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_service_status? +

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

Can I rate-limit get_service_status? +

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

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

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