특정 Velog 포스트의 댓글 목록을 가져옵니다. 댓글 ID를 확인하여 삭제에 활용할 수 있습니다. username을 지정하면 타 유저 포스트의 댓글도 조회할 수 있습니다.
AI agents call velog_get_comments to retrieve information from Velog without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a query/retrieval operation with no data modification capabilities. While it can access comments from other users' posts via username parameter, it only reads data without creating, modifying, or deleting anything. The mention of comment ID retrieval for potential future deletion does not change the tool's inherent function—it is purely informational.
From the tool's definition Tool retrieves comment list from Velog posts ("댓글 목록을 가져옵니다" = "fetches comment list"). Supports querying by username and comment ID retrieval, but performs no modifications, deletions, or side effects.
Documented attack patterns abuse exactly the kind of access velog_get_comments 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_get_comments:
{
"version": "1",
"default": "deny",
"tools": {
"velog_get_comments": {}
}
}velog_get_comments is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
특정 Velog 포스트의 댓글 목록을 가져옵니다. 댓글 ID를 확인하여 삭제에 활용할 수 있습니다. username을 지정하면 타 유저 포스트의 댓글도 조회할 수 있습니다. It is categorised as a Read tool in the Velog MCP Server, which means it retrieves data without modifying state.
Register the Velog MCP server in PolicyLayer and add a rule for velog_get_comments: 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_get_comments 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 velog_get_comments 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_get_comments. 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_get_comments 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.