Get account-level metrics for a profile URL — { platform, handle, name, followers, following, posts, likes, verified, avatar }. Live: YouTube channels (subscribers), TikTok users (exact counts + total hearts), Instagram accounts (exact counts), Facebook pages (page followers), X accounts (followe...
AI agents call profile 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 profile URL (e.g. youtube.com/@handle, tiktok.com/@user, instagram.com/user). |
Parameters from the server's own tool schema.
This tool queries and retrieves publicly available social media profile statistics without side effects. No data is created, modified, deleted, or executed. The operation is purely informational retrieval from public sources, making it a Read category tool with low severity risk.
From the tool's definition The tool description states it retrieves account-level metrics (followers, following, posts, likes, verified, avatar) from public profile URLs.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
Get account-level metrics for a profile URL — { platform, handle, name, followers, following, posts, likes, verified, avatar }. Live: YouTube channels (subscribers), TikTok users (exact counts + total hearts), Instagram accounts (exact counts), Facebook pages (page followers), X accounts (followers/following/posts), Bluesky accounts (exact counts), Mastodon accounts (exact, major instances). Threads, LinkedIn, and login-walled Facebook need a session cookie. It is categorised as a Read tool in the Pulse MCP Server, which means it retrieves data without modifying state.
profile 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 profile: 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.
profile 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 profile 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 profile. 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.
profile 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 →