자주 쓰는 텍스트를 스니펫으로 저장합니다.
AI agents use clip_snippet_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.
This tool creates and stores new clipboard snippet entries in what appears to be a local personal database or clipboard manager. It modifies data reversibly—snippets can be updated, deleted, or cleared. There is no irreversible deletion, financial transaction, code execution, or external command invocation.
From the tool's definition Tool name 'clip_snippet_add' combined with description indicating it saves frequently-used text as snippets ('자주 쓰는 텍스트를 스니펫으로 저장합니다' = 'saves frequently-used text as snippets'). The verb 'add' and 'save' indicate data creation/modification.
Attacks that exploit this kind of access
자주 쓰는 텍스트를 스니펫으로 저장합니다. 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.
Register the K-Personal MCP server in PolicyLayer and add a rule for clip_snippet_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.
clip_snippet_add is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the clip_snippet_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.
Set action: deny in the PolicyLayer policy for clip_snippet_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.
clip_snippet_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.
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 →