AI agents use add-mood to create or update resources in Habitify — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Habitify environment.
This tool creates new mood data entries. It is categorized as Write rather than Read (it modifies state) or Destructive (mood entries can be deleted or corrected). The severity is medium because an AI agent could spam mood entries or add misleading emotional data, but the impact is limited to the user's personal mood log and reversible.
From the tool's definition Tool name is 'add-mood' with description 'Add mood entry'. The 'add' verb combined with 'mood entry' indicates creation of new data.
Documented attack patterns abuse exactly the kind of access add-mood gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Habitify, and nothing reaches the server without passing your rules. This is the rule we recommend for add-mood:
{
"version": "1",
"default": "deny",
"tools": {
"add-mood": {
"limits": [
{
"counter": "add-mood_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add-mood 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.
Add mood entry. It is categorised as a Write tool in the Habitify MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Habitify MCP server in PolicyLayer and add a rule for add-mood: 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 Habitify. Nothing to install.
add-mood 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 add-mood 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 add-mood. 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.
add-mood is provided by the Habitify MCP server (sargonpiraev/habitify-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Habitify, 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.
12 Habitify tools catalogued and risk-classified — across an index of 43,000+ MCP servers.