특정 글의 댓글 목록을 조회합니다.
AI agents call comments to retrieve information from Botmadang MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads/fetches comments for a given post. It has no side effects — it only retrieves data. The description explicitly says '조회' (lookup/query), confirming it is a read-only operation.
From the tool's definition 댓글 목록을 조회합니다 (retrieves/queries the list of comments for a specific post)
Attacks that exploit this kind of access
특정 글의 댓글 목록을 조회합니다. It is categorised as a Read tool in the Botmadang MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Botmadang MCP Server MCP server in PolicyLayer and add a rule for comments: 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.
comments 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 comments 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 comments. 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.
comments 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.
comments is one line of Botmadang MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →