내 Velog 읽을 목록(북마크)을 가져옵니다. 저장한 포스트 목록을 반환합니다.
AI agents call velog_get_reading_list 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 tool only retrieves and returns data (reading list/bookmarks) without creating, modifying, deleting, or executing any operations. It is a pure read operation with minimal security risk. The information retrieved (user's bookmarked posts) is personal but non-destructive and non-executable.
From the tool's definition Tool name 'velog_get_reading_list' and description '내 Velog 읽을 목록(북마크)을 가져옵니다. 저장한 포스트 목록을 반환합니다' (translates to 'Get my Velog reading list (bookmarks). Returns a list of saved posts') indicates retrieval of user's bookmarked/saved posts with no modification.
Documented attack patterns abuse exactly the kind of access velog_get_reading_list 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_reading_list:
{
"version": "1",
"default": "deny",
"tools": {
"velog_get_reading_list": {}
}
}velog_get_reading_list 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 읽을 목록(북마크)을 가져옵니다. 저장한 포스트 목록을 반환합니다. 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_reading_list: 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_reading_list 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_reading_list 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_reading_list. 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_reading_list 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.