db_todo_done · K-Personal MCP: Risk & Policy

WHAT IT DOES

What db_todo_done does on K-Personal MCP

AI agents use db_todo_done 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_todo_done needs a policy

The tool writes to a personal database by changing a todo's status to completed. This is a reversible modification (the status can presumably be changed back), so it falls under Write rather than Destructive. The severity is low because it only affects personal todo data with no external impact, financial consequences, or ability to execute arbitrary code.

From the tool's definition Tool name 'db_todo_done' and description indicating completion of a todo item ('할 일을 완료 처리합니다' = 'Marks a todo as completed'). This modifies state in a personal SQLite database by updating a todo record.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

db_todo_done Rate-limited

db_todo_done 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_todo_done": {
      "limits": [
        {
          "counter": "db_todo_done_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_todo_done

What does the db_todo_done 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_todo_done? +

Register the K-Personal MCP server in PolicyLayer and add a rule for db_todo_done: 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_todo_done? +

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

Can I rate-limit db_todo_done? +

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

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

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