db_schedule_add · K-Personal MCP: Risk & Policy

WHAT IT DOES

What db_schedule_add does on K-Personal MCP

AI agents use db_schedule_add 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_schedule_add needs a policy

This tool creates or adds new data (schedule entries) to a database in a reversible manner. It does not execute actions, delete data, or trigger financial operations. Write category applies because it modifies the database state by adding new records. Severity is medium because misuse could clutter the schedule database or create unwanted task entries, but these effects are reversible and have limited blast radius.

From the tool's definition Tool name 'db_schedule_add' and description indicating it registers/adds recurring/scheduled items to what appears to be a personal database. The Korean text translates roughly to: 'Registers recurring/scheduled events.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

db_schedule_add Rate-limited

db_schedule_add 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_schedule_add": {
      "limits": [
        {
          "counter": "db_schedule_add_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_schedule_add

What does the db_schedule_add tool do? +

반복/예약 일정을 등록합니다. 실제 자동 실행은 하지 않으며, K 가 다음에. 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_schedule_add? +

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

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

Can I rate-limit db_schedule_add? +

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

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

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