home-assistant.health

Check that Home Assistant is reachable and the token works. Returns the instance version and which service calls are allowlisted.

SERVERCoWork OS SOURCECoWork-OS/CoWork-OS

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cowork-os/home-assistant.health.md

WHAT IT DOES

What home-assistant.health does on CoWork OS

AI agents use home-assistant.health to create or update resources in CoWork OS, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CoWork OS environment.

RISK

Why home-assistant.health is rated Medium

An AI agent can call home-assistant.health faster than any human can review: one bad instruction and it creates or modifies resources in CoWork OS by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs home-assistant.health safely

PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For home-assistant.health, this is the rule to start with:

home-assistant.health Rate-limited

home-assistant.health stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "home-assistant.health": {
      "limits": [
        {
          "counter": "home-assistant.health_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect CoWork OS, apply this rule, and every home-assistant.health call is checked against it from then on.

FAQ

Questions about home-assistant.health

What does the home-assistant.health tool do? +

Check that Home Assistant is reachable and the token works. Returns the instance version and which service calls are allowlisted. It is categorised as a Write tool in the CoWork OS MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on home-assistant.health? +

Register the CoWork OS MCP server in PolicyLayer and add a rule for home-assistant.health: 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 CoWork OS. Nothing to install.

What risk level is home-assistant.health? +

home-assistant.health is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit home-assistant.health? +

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

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

home-assistant.health is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CoWork OS, and thousands of servers like it.

This server

All 354 CoWork OS tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →