현재 토큰 소유자(나)의 정보를 조회합니다.
AI agents call get_current_user 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 queries and retrieves user information about the authenticated user. It has no side effects, creates no data modifications, and poses minimal risk. The only data exposed is information about the tool's own caller, which is read-only access typical of identity/profile lookups.
From the tool's definition Tool description states '현재 토큰 소유자(나)의 정보를 조회합니다' (retrieves information about the current token owner). The verb 조회 (jojhoe) means 'to query' or 'to retrieve'. No modification, execution, deletion, or financial operation is involved.
Attacks that exploit this kind of access
현재 토큰 소유자(나)의 정보를 조회합니다. 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_current_user: 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_current_user 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_current_user 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_current_user. 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_current_user 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 →