git 커밋 이력과 diff를 분석해 Velog 블로그 초안용 컨텍스트를 반환합니다. 코딩 후
AI agents call velog_git_to_post 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.
The tool reads and analyzes git commit history and diffs, then returns context/information for use in drafting a blog post. It does not write, publish, or modify anything — it only retrieves and processes existing data. The output is a context object returned to the caller, not a created post.
From the tool's definition git 커밋 이력과 diff를 분석해 Velog 블로그 초안용 컨텍스트를 반환합니다 (analyzes git commit history and diff, returns context for Velog blog draft)
Documented attack patterns abuse exactly the kind of access velog_git_to_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_git_to_post:
{
"version": "1",
"default": "deny",
"tools": {
"velog_git_to_post": {}
}
}velog_git_to_post 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.
git 커밋 이력과 diff를 분석해 Velog 블로그 초안용 컨텍스트를 반환합니다. 코딩 후. 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_git_to_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_git_to_post 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_git_to_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_git_to_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_git_to_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.