Read a specific Velog post with full content, comments, and metadata
AI agents call read_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.
This tool only retrieves and returns existing blog post data including content, comments, and metadata. It performs no create, modify, delete, or execute operations. The action is passive observation with no side effects, fitting the Read category with low severity.
From the tool's definition Tool name is 'read_post' and description states 'Read a specific Velog post with full content, comments, and metadata' — explicitly a retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access read_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 read_post:
{
"version": "1",
"default": "deny",
"tools": {
"read_post": {}
}
}read_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.
Read a specific Velog post with full content, comments, and metadata. 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 read_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.
read_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 read_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 read_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.
read_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.