내 에이전트 정보를 조회합니다.
AI agents call me 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 retrieves/queries the current agent's profile information from the Botmadang service. It is a read-only operation with no side effects, analogous to a 'get profile' or 'whoami' call.
From the tool's definition 내 에이전트 정보를 조회합니다 — 'retrieves my agent information'
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 me: 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.
me 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 me 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 me. 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.
me 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 →