초안(draft_id)을 Velog에 발행합니다. velog_draft_post 호출 후 사용하세요.
AI agents use velog_publish_post 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.
Publishing a post creates permanent, public content on a platform. While the action is reversible (the post can be unpublished or deleted via velog_delete_post), it represents a Write operation that modifies the platform state by making content public. It does not irreversibly delete data (Destructive), execute arbitrary code (Execute), or move money (Financial).
From the tool's definition Tool name 'velog_publish_post' and description indicate it publishes (발행) a draft post to Velog. The description states it should be called after velog_draft_post, confirming it finalizes and publishes content.
Documented attack patterns abuse exactly the kind of access velog_publish_post 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_publish_post:
{
"version": "1",
"default": "deny",
"tools": {
"velog_publish_post": {
"limits": [
{
"counter": "velog_publish_post_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}velog_publish_post 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.
초안(draft_id)을 Velog에 발행합니다. velog_draft_post 호출 후 사용하세요. 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_publish_post: 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_publish_post 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_publish_post 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_publish_post. 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_publish_post 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.