사용자를 이름, username, 닉네임으로 검색합니다.
AI agents call search_users 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 data without side effects. It is a search operation that returns information, matching the Read category. The blast radius is minimal since it only discloses existing user metadata available within the Mattermost system, and no sensitive operations or data modifications are permitted.
From the tool's definition Tool name 'search_users' and description indicating it searches/retrieves user information by name, username, and nickname ('사용자를 이름, username, 닉네임으로 검색합니다' = 'Search users by name, username, nickname').
Attacks that exploit this kind of access
사용자를 이름, 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 search_users: 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.
search_users 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 search_users 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 search_users. 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.
search_users 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 →