블로그용 이미지를 업로드합니다. blog_id와 이미지 파일 경로(file_path)가 필요합니다.
AI agents use upload_blog_image to create or update resources in Wikidocs — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Wikidocs environment.
This tool creates new image resources in the Wikidocs system and modifies blog content by adding images. It is reversible (images can typically be deleted), so it falls under Write rather than Destructive. The severity is medium because unintended image uploads could clutter the blog or introduce inappropriate content, but the blast radius is limited compared to destructive or financial operations.
From the tool's definition Tool description states: '블로그용 이미지를 업로드합니다' (uploads images for blogs). The action is explicitly an upload operation that creates/adds image assets to a blog.
Documented attack patterns abuse exactly the kind of access upload_blog_image gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Wikidocs, and nothing reaches the server without passing your rules. This is the rule we recommend for upload_blog_image:
{
"version": "1",
"default": "deny",
"tools": {
"upload_blog_image": {
"limits": [
{
"counter": "upload_blog_image_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}upload_blog_image 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.
블로그용 이미지를 업로드합니다. blog_id와 이미지 파일 경로(file_path)가 필요합니다. It is categorised as a Write tool in the Wikidocs MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Wikidocs MCP server in PolicyLayer and add a rule for upload_blog_image: 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 Wikidocs. Nothing to install.
upload_blog_image 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 upload_blog_image 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 upload_blog_image. 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.
upload_blog_image is provided by the Wikidocs MCP server (ychoi-kr/wikidocs-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Wikidocs, 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.
17 Wikidocs tools catalogued and risk-classified — across an index of 43,000+ MCP servers.