Create a new post on Velog (requires authentication)
AI agents use write_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.
This tool creates new blog post content on a public platform, which is a reversible Write operation. Severity is high because an AI agent could spam, create misleading content, or impersonate the user at scale if authentication is compromised or misused. It requires authentication, which mitigates but does not eliminate risk.
From the tool's definition Tool name 'write_post' and description 'Create a new post on Velog' indicate creation of new data. The server description confirms 'write Velog blog posts' and 'post management' capabilities.
Documented attack patterns abuse exactly the kind of access write_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 write_post:
{
"version": "1",
"default": "deny",
"tools": {
"write_post": {
"limits": [
{
"counter": "write_post_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}write_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.
Create a new post on Velog (requires authentication). 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 write_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.
write_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 write_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 write_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.
write_post is provided by the Velog MCP server (stonehee99/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.
10 Velog tools catalogued and risk-classified — across an index of 43,000+ MCP servers.