get_x_post_metrics
Get engagement metrics for a tweet on X (Twitter). Returns impressions, likes, retweets, replies, quotes, and bookmarks. Use when the user asks "how did my post do?", "check my tweet analytics", or to evaluate content performance.
This record as markdown: /tools/com-getfreedomos-freedom-mcp/get-x-post-metrics.md
What get_x_post_metrics does on Freedom Mcp
AI agents call get_x_post_metrics to retrieve information from Freedom Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
tweet_id | string | Yes | The tweet ID (numeric) or full tweet URL (e.g. https://x.com/user/status/123456) |
companyId | string | Yes | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
pipeline_output_id | string | — | Optional. The pipeline_output ID to write metrics back to the content card. |
Parameters from the server's own tool schema.
Why get_x_post_metrics is rated Low
This tool queries social media analytics and returns read-only performance data about existing content. No creation, modification, deletion, code execution, or financial operations occur. The blast radius of misuse is minimal — an attacker could view analytics for posts they shouldn't see, but cannot alter content, execute actions, or cause harm beyond information disclosure.
From the tool's definition Tool retrieves engagement metrics (impressions, likes, retweets, replies, quotes, bookmarks) for existing posts. Description uses "Get" and "Returns" — indicates data retrieval with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_x_post_metrics safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Freedom Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_x_post_metrics, this is the rule to start with:
get_x_post_metrics is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Freedom Mcp, apply this rule, and every get_x_post_metrics call is checked against it from then on.
Questions about get_x_post_metrics
Get engagement metrics for a tweet on X (Twitter). Returns impressions, likes, retweets, replies, quotes, and bookmarks. Use when the user asks "how did my post do?", "check my tweet analytics", or to evaluate content performance. It is categorised as a Read tool in the Freedom Mcp MCP Server, which means it retrieves data without modifying state.
get_x_post_metrics accepts 3 parameters: tweet_id, companyId, pipeline_output_id. Required: tweet_id, companyId. The full parameter table on this page comes from the server's own tool schema.
Register the Freedom MCP server in PolicyLayer and add a rule for get_x_post_metrics: 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 Freedom Mcp. Nothing to install.
get_x_post_metrics 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_x_post_metrics 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_x_post_metrics. 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_x_post_metrics is provided by the Freedom MCP server (https://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Freedom, and thousands of servers like it.
This server
Across the catalogue