db_habit_check · K-Personal MCP: Risk & Policy

WHAT IT DOES

What db_habit_check does on K-Personal MCP

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

WHY IT NEEDS A POLICY

Why db_habit_check needs a policy

This tool writes a completion record for a daily habit to the local SQLite database. It modifies data (marks a habit as done) but this is reversible and low blast radius — it only affects personal habit tracking data.

From the tool's definition '완료 체크합니다' means 'marks as complete' — it records a habit completion for today in the SQLite database

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

db_habit_check Rate-limited

db_habit_check 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": {
    "db_habit_check": {
      "limits": [
        {
          "counter": "db_habit_check_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 K-Personal MCP, so you can run agents against it safely.

FAQ

Questions about db_habit_check

What does the db_habit_check tool do? +

오늘 습관을 완료 체크합니다. It is categorised as a Write tool in the K-Personal MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on db_habit_check? +

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

What risk level is db_habit_check? +

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

Can I rate-limit db_habit_check? +

Yes. Add a rate_limit block to the db_habit_check 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 db_habit_check completely? +

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

db_habit_check is provided by the K-Personal MCP server (lee30934-byte/k-personal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.