get_thread_posts
AI agents call get_thread_posts to retrieve information from Mcp Metricool without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix combined with the pattern of sibling tools all performing metric and post retrieval operations indicates this tool retrieves post data without modification or execution. This is a standard Read operation with low blast radius if misused—an agent could retrieve unwanted data but cannot modify, delete, or execute operations.
From the tool's definition Tool name 'get_thread_posts' indicates retrieval of post data. Sibling tools on the same server (get_bluesky_posts, get_facebook_posts, get_instagram_posts, etc.) all follow a 'get_*' pattern consistent with read-only data retrieval.
Attacks that exploit this kind of access
get_thread_posts. It is categorised as a Read tool in the Mcp Metricool MCP Server, which means it retrieves data without modifying state.
Register the Mcp Metricool MCP server in PolicyLayer and add a rule for get_thread_posts: 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 Mcp Metricool. Nothing to install.
get_thread_posts 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_thread_posts 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_thread_posts. 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_thread_posts is provided by the Mcp Metricool MCP server (namdzmaso02/mcp-metricool). 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 →