log_entry · Jhabit MCP: Risk & Policy

WHAT IT DOES

What log_entry does on Jhabit

AI agents use log_entry to create or update resources in Jhabit — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Jhabit environment.

WHY IT NEEDS A POLICY

Why log_entry needs a policy

This tool creates a new entry (log record) associated with a tracker. It is a data creation operation that is reversible (entries can be deleted via the sibling delete_entry tool), placing it in the Write category. Misuse could pollute habit tracking history but is recoverable, warranting medium severity.

From the tool's definition "Log an entry for a tracker" — creates a new log/entry record for a habit tracker

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

log_entry Rate-limited

log_entry 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "log_entry": {
      "limits": [
        {
          "counter": "log_entry_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Jhabit, so you can run agents against it safely.

FAQ

Questions about log_entry

What does the log_entry tool do? +

Log an entry for a tracker. For habits this means. It is categorised as a Write tool in the Jhabit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on log_entry? +

Register the Jhabit MCP server in PolicyLayer and add a rule for log_entry: 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 Jhabit. Nothing to install.

What risk level is log_entry? +

log_entry is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit log_entry? +

Yes. Add a rate_limit block to the log_entry 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.

How do I block log_entry completely? +

Set action: deny in the PolicyLayer policy for log_entry. 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.

What MCP server provides log_entry? +

log_entry is provided by the Jhabit MCP server (jacob-stokes/jhabit-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.