특정 게시물의 전체 스레드를 가져옵니다. 결과에는 자동으로 작성자의 이름(user_name)과 username이 포함됩니다.
AI agents call get_post_thread 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 existing message thread data from Mattermost without creating, modifying, deleting, or executing operations. It is a straightforward data retrieval function analogous to 'get_channel_messages' on the same server. The blast radius of misuse is limited to information disclosure.
From the tool's definition Tool retrieves thread content with 'get_post_thread' (retrieves, no modification described) and description states '특정 게시물의 전체 스레드를 가져옵니다' (retrieves the entire thread of a specific post).
Attacks that exploit this kind of access
특정 게시물의 전체 스레드를 가져옵니다. 결과에는 자동으로 작성자의 이름(user_name)과 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_post_thread: 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_post_thread 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_post_thread 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_post_thread. 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_post_thread 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 →