AI agents use read_notification to create or update resources in Habitca — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Habitca environment.
Marking a notification as read modifies its state (read/unread) in the system. This is a reversible write operation with minimal blast radius — it changes notification state but does not delete data or have financial/destructive consequences.
From the tool's definition Mark a notification as read
Attacks that exploit this kind of access
Mark a notification as read. It is categorised as a Write tool in the Habitca MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Habitca MCP server in PolicyLayer and add a rule for read_notification: 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 Habitca. Nothing to install.
read_notification 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 read_notification 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 read_notification. 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.
read_notification is provided by the Habitca MCP server (leon-jarvis1/habitca_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 →