Send notifications through Home Assistant notification services.
AI agents use notify to create or update resources in HomeAssistant MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your HomeAssistant MCP environment.
This tool creates and sends notification messages, which is a reversible write operation. While notifications are transmitted, they do not modify persistent system state, delete data, execute code, move money, or trigger physical actions. The blast radius is minimal—a misused notification might spam users but causes no lasting harm or system compromise.
From the tool's definition Tool name 'notify' and description 'Send notifications through Home Assistant notification services' indicate creation/transmission of data (notification messages) with no irreversible data loss or external financial/physical consequence.
Documented attack patterns abuse exactly the kind of access notify gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and HomeAssistant MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for notify:
{
"version": "1",
"default": "deny",
"tools": {
"notify": {
"limits": [
{
"counter": "notify_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}notify 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.
Free to start. No card required.
Send notifications through Home Assistant notification services. It is categorised as a Write tool in the HomeAssistant MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the HomeAssistant MCP server in PolicyLayer and add a rule for notify: 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 HomeAssistant MCP. Nothing to install.
notify is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the notify 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.
Set action: deny in the PolicyLayer policy for notify. 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.
notify is provided by the HomeAssistant MCP server (jango-blockchained/advanced-homeassistant-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from HomeAssistant MCP, 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.
13 HomeAssistant MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.