지금 도래한 일정만 봅니다(읽기전용). K 상호작용 시작 시 점검용.
AI agents call db_schedule_due to retrieve information from K-Personal MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool is explicitly described as read-only, retrieving due schedules from the personal SQLite database without any side effects. It is intended as a check at the start of interactions.
From the tool's definition 지금 도래한 일정만 봅니다(읽기전용) — translates to 'View only schedules that are due now (read-only)'
Attacks that exploit this kind of access
지금 도래한 일정만 봅니다(읽기전용). K 상호작용 시작 시 점검용. It is categorised as a Read tool in the K-Personal MCP MCP Server, which means it retrieves data without modifying state.
Register the K-Personal MCP server in PolicyLayer and add a rule for db_schedule_due: 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.
db_schedule_due is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the db_schedule_due 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 db_schedule_due. 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.
db_schedule_due 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →