Get account-level metrics for many profile URLs in one call — same as profile but up to 50 URLs at once. Mixed platforms welcome (YouTube, TikTok, Instagram, Facebook, X, Bluesky, Mastodon). Returns { count, results }, order preserved — each result is a profile object or { url, error }. Useful fo...
AI agents call profile_batch 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 |
|---|---|---|---|
urls | array | Yes | Profile URLs (max 50, mixed platforms OK). |
Parameters from the server's own tool schema.
This tool only queries and retrieves publicly available social media profile statistics without modifying, executing operations, deleting data, or moving money. It is a straightforward read operation that aggregates profile metrics across multiple URLs. The blast radius of misuse is minimal—an attacker could profile many accounts to map social networks or identify targets, but cannot modify or delete data.
From the tool's definition Tool 'profile_batch' retrieves 'account-level metrics' (follower counts, etc.) from 'public post URLs' and 'returns { count, results }' with profile data.
Attacks that exploit this kind of access
Get account-level metrics for many profile URLs in one call — same as profile but up to 50 URLs at once. Mixed platforms welcome (YouTube, TikTok, Instagram, Facebook, X, Bluesky, Mastodon). Returns { count, results }, order preserved — each result is a profile object or { url, error }. Useful for comparing follower counts across a list of creators/accounts. It is categorised as a Read tool in the Pulse MCP Server, which means it retrieves data without modifying state.
profile_batch accepts 1 parameter: urls. Required: urls. 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_batch: 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_batch 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_batch 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_batch. 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_batch 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.
profile_batch is one line of Pulse's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →