get_mattermost_users
AI agents call get_mattermost_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.
The tool name and prefix pattern ('get_') indicate this retrieves user data from Mattermost. There is no evidence it modifies, deletes, or executes operations. It aligns with other retrieval tools on the same server. The empty description reduces confidence slightly, but the naming convention and server context are sufficient to classify it as Read.
From the tool's definition Tool name 'get_mattermost_users' indicates a retrieval operation. Context shows sibling tools include 'get_mattermost_channel_history', 'get_mattermost_user_profile', and 'list_mattermost_channels', which are all Read-category tools.
Attacks that exploit this kind of access
get_mattermost_users. 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_mattermost_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.
get_mattermost_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 get_mattermost_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 get_mattermost_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.
get_mattermost_users is provided by the Mattermost MCP Server MCP server (vnikhilbuddhavarapu/mattermost-gcp-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 →