Get metrics for many posts and/or profiles in one call. Pass an array of URLs (max 50, mixed post and profile URLs welcome); returns { count, results }, order preserved — each result is the metrics object or { url, error }.
AI agents call metrics_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 | Public post URLs (max 50). |
Parameters from the server's own tool schema.
This tool queries public data and returns aggregated metrics without side effects. It is a batch retrieval operation that does not create, modify, delete, or execute any operations. The data source is explicitly public, and the operation is read-only.
From the tool's definition Tool fetches and retrieves social media metrics (views, likes, comments) from public post URLs. Description explicitly states it 'Get metrics for many posts and/or profiles' and returns metrics objects.
Attacks that exploit this kind of access
Get metrics for many posts and/or profiles in one call. Pass an array of URLs (max 50, mixed post and profile URLs welcome); returns { count, results }, order preserved — each result is the metrics object or { url, error }. It is categorised as a Read tool in the Pulse MCP Server, which means it retrieves data without modifying state.
metrics_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 metrics_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.
metrics_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 metrics_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 metrics_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.
metrics_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.
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 →