AI agents use add-habit-log 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.
The tool creates or modifies data (habit logs) in a reversible manner. It does not execute arbitrary code, delete data permanently, or involve financial transactions. Write operations that modify user data have medium severity because misuse could generate unwanted entries, but the effects are reversible through the sibling delete-habit-log tool.
From the tool's definition Tool name 'add-habit-log' and description 'Add a habit log' indicate creation of new data records in the Habitify system. This is a write operation that creates new habit log entries.
Documented attack patterns abuse exactly the kind of access add-habit-log 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-habit-log:
{
"version": "1",
"default": "deny",
"tools": {
"add-habit-log": {
"limits": [
{
"counter": "add-habit-log_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add-habit-log 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 a habit log. 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-habit-log: 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-habit-log 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-habit-log 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-habit-log. 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-habit-log 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.