GitHub 블로그 저장소의 마크다운 파일을 Velog 초안으로 가져옵니다. Jekyll/Hugo/기타 정적 블로그의 _posts 폴더를 지원합니다. dry_run: true로 먼저 미리보기를 확인하세요.
AI agents use velog_import_from_github 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 draft posts by importing content from GitHub repositories. While the action is reversible (drafts can be deleted) and requires user approval before publication, it still modifies the Velog platform by adding new draft content. This fits the Write category (creates or modifies data reversibly).
From the tool's definition Tool name 'velog_import_from_github' and description indicate it imports markdown files from GitHub into Velog as drafts ('Velog 초안으로 가져옵니다'). The operation creates new draft posts in the Velog platform, which is a reversible creation/modification action.
Documented attack patterns abuse exactly the kind of access velog_import_from_github 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_import_from_github:
{
"version": "1",
"default": "deny",
"tools": {
"velog_import_from_github": {
"limits": [
{
"counter": "velog_import_from_github_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}velog_import_from_github 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.
GitHub 블로그 저장소의 마크다운 파일을 Velog 초안으로 가져옵니다. Jekyll/Hugo/기타 정적 블로그의 _posts 폴더를 지원합니다. dry_run: true로 먼저 미리보기를 확인하세요. 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_import_from_github: 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_import_from_github 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_import_from_github 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_import_from_github. 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_import_from_github 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.