Velog 포스트에 댓글을 작성합니다. comment_id를 지정하면 대댓글로 작성됩니다.
AI agents use velog_write_comment to create or update resources in Velog — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Velog environment.
This tool creates new comment data on a user's Velog platform. While comments are typically modifiable or deletable (reversible), the action itself is Write category—it adds user-generated content to the platform. The presence of a sibling tool 'velog_delete_comment' confirms comments can be removed, further supporting Write rather than Destructive classification.
From the tool's definition Tool description states '포스트에 댓글을 작성합니다' (writes/posts comments on Velog posts). The capability to write comments with optional nesting (대댓글, reply comments when comment_id is specified) is a reversible content creation action.
Documented attack patterns abuse exactly the kind of access velog_write_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_write_comment:
{
"version": "1",
"default": "deny",
"tools": {
"velog_write_comment": {
"limits": [
{
"counter": "velog_write_comment_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}velog_write_comment 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.
Free to start. No card required.
Velog 포스트에 댓글을 작성합니다. comment_id를 지정하면 대댓글로 작성됩니다. It is categorised as a Write tool in the Velog MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Velog MCP server in PolicyLayer and add a rule for velog_write_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_write_comment 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 velog_write_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_write_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_write_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.