AI agents call velog_delete_comment to permanently remove resources in Velog — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes comments, which cannot be undone. It is categorized as Destructive rather than Execute because the action (deletion) is inherently irreversible. The severity is high because unauthorized deletion of comments could damage user relationships, reputation, or content integrity on the platform, though the blast radius is narrower than full post deletion.
From the tool's definition Tool name 'velog_delete_comment' and description 'Velog 댓글을 삭제합니다' (deletes a Velog comment) indicate permanent deletion of user-generated content.
Documented attack patterns abuse exactly the kind of access velog_delete_comment gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Velog, and nothing reaches the server without passing your rules. This is the rule we recommend for velog_delete_comment:
{
"version": "1",
"default": "deny",
"hide": [
"velog_delete_comment"
]
}velog_delete_comment disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Velog 댓글을 삭제합니다. It is categorised as a Destructive tool in the Velog MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Velog MCP server in PolicyLayer and add a rule for velog_delete_comment: 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 Velog. Nothing to install.
velog_delete_comment is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the velog_delete_comment 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 velog_delete_comment. 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.
velog_delete_comment is provided by the Velog MCP server (seongwon030/velog_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Velog, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
29 Velog tools catalogued and risk-classified — across an index of 43,000+ MCP servers.