사용자 ID로 사용자의 상세 정보를 조회합니다. username, 이름, 닉네임 등을 확인할 수 있습니다.
AI agents call get_user_info to retrieve information from Mattermost 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 user information without creating, modifying, deleting, or executing any actions. It is a pure data retrieval operation that returns user profile details. The narrow scope (single user by ID) and read-only nature result in low severity. High confidence due to clear retrieval semantics and alignment with sibling read tools (get_current_user, search_users).
From the tool's definition Tool description states it '조회합니다' (retrieves/queries) user details by user ID, retrieving username, name, nickname and other information. The verb 조회 indicates a read-only query operation with no modification capability.
Attacks that exploit this kind of access
사용자 ID로 사용자의 상세 정보를 조회합니다. username, 이름, 닉네임 등을 확인할 수 있습니다. It is categorised as a Read tool in the Mattermost MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Mattermost MCP Server MCP server in PolicyLayer and add a rule for get_user_info: 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 Mattermost MCP Server. Nothing to install.
get_user_info 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_info 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_info. 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_info is provided by the Mattermost MCP Server MCP server (jhanglim/mattermost-mcp-server). 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 →