Get a public social post's metrics. Give a post URL (YouTube, X/Twitter incl. view counts, TikTok incl. photo posts, Bluesky, Mastodon (major instances), Hacker News (points + comments), Stack Overflow (views + score + answers), Instagram, Threads, LinkedIn — short links like vm.tiktok.com and t....
AI agents call metrics to retrieve information from Pulse without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | The public post URL (short links OK). |
Parameters from the server's own tool schema.
This tool only queries and returns publicly available social media metrics from post URLs. It performs no modifications, deletions, code execution, or financial operations. The retrieval of public metrics from unprotected social media posts presents minimal risk; the worst case is data exfiltration of already-public information.
From the tool's definition Tool description explicitly states it 'Get[s] a public social post's metrics' and 'get normalized { platform, views, likes, comments, shares, quotes, bookmarks, publishedAt, title, author, thumbnail }' — purely retrieves publicly available data with no side…
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
Get a public social post's metrics. Give a post URL (YouTube, X/Twitter incl. view counts, TikTok incl. photo posts, Bluesky, Mastodon (major instances), Hacker News (points + comments), Stack Overflow (views + score + answers), Instagram, Threads, LinkedIn — short links like vm.tiktok.com and t.co resolve automatically) and get normalized { platform, views, likes, comments, shares, quotes, bookmarks, publishedAt, title, author, thumbnail } — shares = reshares (X retweets, TikTok shares, Bluesky reposts); quotes = quote posts (X, Bluesky); bookmarks = saves (X). Free. It is categorised as a Read tool in the Pulse MCP Server, which means it retrieves data without modifying state.
metrics accepts 1 parameter: url. Required: url. The full parameter table on this page comes from the server's own tool schema.
Register the Pulse MCP server in PolicyLayer and add a rule for 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 Pulse. Nothing to install.
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 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 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.
metrics is provided by the Pulse MCP server (pulse-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 →