Get system notifications
AI agents call get_notifications to retrieve information from HC3 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves/queries notification data from the HC3 smart home system. It performs no writes, deletes, executions, or financial operations. The blast radius of misuse is minimal—an agent could only read existing notifications, which poses no meaningful risk to the system, devices, or user data integrity.
From the tool's definition Tool name is 'get_notifications' and description states 'Get system notifications' — pure retrieval with no side effects, data modification, or external operations triggered.
Attacks that exploit this kind of access
Get system notifications. It is categorised as a Read tool in the HC3 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the HC3 MCP Server MCP server in PolicyLayer and add a rule for get_notifications: 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 HC3 MCP Server. Nothing to install.
get_notifications is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_notifications 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 get_notifications. 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.
get_notifications is provided by the HC3 MCP Server MCP server (jangabrielsson/hc3_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →