Get the recorded metrics history of a post OR a profile — the growth curve. Every fresh metrics fetch records a { t, views, likes, comments, shares, quotes, bookmarks } snapshot (profiles: { t, followers, posts }); this returns the series (oldest first). Pass since (ISO-8601 or unix ms) to get on...
AI agents call history 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 or profile URL. |
since | string | — | Optional — ISO-8601 date or unix milliseconds; only points after this moment are returned. |
Parameters from the server's own tool schema.
This tool only reads and returns previously recorded metric snapshots. It performs no writes, deletions, or executions. The only notable instruction is to call `metrics` or `profile` to initiate tracking, but the `history` tool itself is read-only. Misuse potential is minimal — it exposes public social media metrics with no financial, destructive, or privacy-sensitive implications beyond what is already public.
From the tool's definition 'Get the recorded metrics history of a post OR a profile — the growth curve' and 'this returns the series (oldest first)' — purely retrieves stored historical data with no side effects
Risk signalsAccepts URL/endpoint input (url) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Get the recorded metrics history of a post OR a profile — the growth curve. Every fresh metrics fetch records a { t, views, likes, comments, shares, quotes, bookmarks } snapshot (profiles: { t, followers, posts }); this returns the series (oldest first). Pass since (ISO-8601 or unix ms) to get only the points after that moment — poll the delta, not the whole series. An empty series means the URL hasn't been fetched yet: call metrics or profile on it to start the series. It is categorised as a Read tool in the Pulse MCP Server, which means it retrieves data without modifying state.
history accepts 2 parameters: url, since. 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 history: 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.
history 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 history 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 history. 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.
history 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 →