Gets performance metrics for a specific Threads post. Args: - media_id (string): Threads media ID - metrics (string[]): Metrics to retrieve. Options: views, likes, replies, reposts, quotes, shares, reach, saved Returns: Metric values for the post.
AI agents call threads_get_post_insights to retrieve information from Meta MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves analytics/performance data without creating, modifying, deleting, or executing operations. It is purely a read operation that queries existing post metrics. There is minimal risk of misuse—an agent could at worst retrieve insights for posts it has access to, but cannot modify content, delete data, or trigger external operations.
From the tool's definition Tool name 'threads_get_post_insights' and description 'Gets performance metrics for a specific Threads post' indicate a retrieval operation. The return value is 'Metric values for the post' with no side effects.
Documented attack patterns abuse exactly the kind of access threads_get_post_insights gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Meta MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for threads_get_post_insights:
{
"version": "1",
"default": "deny",
"tools": {
"threads_get_post_insights": {}
}
}threads_get_post_insights is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Gets performance metrics for a specific Threads post. Args: - media_id (string): Threads media ID - metrics (string[]): Metrics to retrieve. Options: views, likes, replies, reposts, quotes, shares, reach, saved Returns: Metric values for the post. It is categorised as a Read tool in the Meta MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Meta MCP Server MCP server in PolicyLayer and add a rule for threads_get_post_insights: 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 Meta MCP Server. Nothing to install.
threads_get_post_insights 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 threads_get_post_insights 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 threads_get_post_insights. 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.
threads_get_post_insights is provided by the Meta MCP Server MCP server (oliverames/meta-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Meta MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
200 Meta MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.