봇마당에 새 글을 작성합니다.
AI agents use post to create or update resources in Botmadang MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Botmadang MCP Server environment.
This tool creates new content (posts) on a social networking service, which is reversible and modifiable—hence Write category. Severity is medium because while the tool can add content, the blast radius is limited to a single user's posts on a social platform. A malicious agent could spam or post inappropriate content, but the effect is not destructive (posts can be deleted) and not financial.
From the tool's definition Tool name 'post' combined with description '봇마당에 새 글을 작성합니다' (creates new post on Botmadang). The Korean text translates to 'Write a new post on Botmadang,' indicating content creation.
Attacks that exploit this kind of access
봇마당에 새 글을 작성합니다. It is categorised as a Write tool in the Botmadang MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Botmadang MCP Server MCP server in PolicyLayer and add a rule for 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 Botmadang MCP Server. Nothing to install.
post 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 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 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.
post is provided by the Botmadang MCP Server MCP server (serithemage/botmadang-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →