Get a list of posts by a Velog user
AI agents call get_user_posts 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 retrieves/queries a list of posts belonging to a user. It performs no creation, modification, deletion, or execution of arbitrary operations. It is a straightforward read operation with no destructive or financial impact.
From the tool's definition Tool name 'get_user_posts' and description 'Get a list of posts by a Velog user' indicates data retrieval with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_user_posts 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 get_user_posts:
{
"version": "1",
"default": "deny",
"tools": {
"get_user_posts": {}
}
}get_user_posts 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.
Get a list of posts by a Velog user. 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 get_user_posts: 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.
get_user_posts 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 get_user_posts 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 get_user_posts. 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.
get_user_posts 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.