vibecontrols_analytics_overview
Get consolidated analytics overview with KPIs, time series, and breakdowns for all VibeControls entities (agents, sessions, vibes, actions, webhooks, AI events, vibe decks, audit, docs, notes, config).
This record as markdown: /tools/vibecontrols-mcp/vibecontrols-analytics-overview.md
What vibecontrols_analytics_overview does on Vibecontrols
AI agents call vibecontrols_analytics_overview to retrieve information from Vibecontrols without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
vibeId | string | — | Filter analytics by vibe ID |
agentId | string | — | Filter analytics by agent ID |
endDate | string | — | End date (ISO format). Defaults to now. |
startDate | string | — | Start date (ISO format). Defaults to 7 days ago. |
entityTypes | array | — | Filter to specific entity types (null = all) |
granularity | string | — | Time series granularity |
Parameters from the server's own tool schema.
Why vibecontrols_analytics_overview is rated Low
Even though vibecontrols_analytics_overview only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs vibecontrols_analytics_overview safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Vibecontrols, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For vibecontrols_analytics_overview, this is the rule to start with:
vibecontrols_analytics_overview is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Vibecontrols, apply this rule, and every vibecontrols_analytics_overview call is checked against it from then on.
Questions about vibecontrols_analytics_overview
Get consolidated analytics overview with KPIs, time series, and breakdowns for all VibeControls entities (agents, sessions, vibes, actions, webhooks, AI events, vibe decks, audit, docs, notes, config). It is categorised as a Read tool in the Vibecontrols MCP Server, which means it retrieves data without modifying state.
vibecontrols_analytics_overview accepts 6 parameters: vibeId, agentId, endDate, startDate, entityTypes, granularity. The full parameter table on this page comes from the server's own tool schema.
Register the Vibecontrols MCP server in PolicyLayer and add a rule for vibecontrols_analytics_overview: 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 Vibecontrols. Nothing to install.
vibecontrols_analytics_overview 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 vibecontrols_analytics_overview 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 vibecontrols_analytics_overview. 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.
vibecontrols_analytics_overview is provided by the Vibecontrols MCP server (@vibecontrols/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vibecontrols, and thousands of servers like it.
This server
Across the catalogue