Retrieve aggregated summary statistics for log spans. Returns total_count, total_cost, total_tokens, avg_latency etc. Useful for getting quick insights into your LLM usage without fetching all individual spans. PARAMETERS: - start_time: Start time in ISO 8601 format (required) - end_time: End tim...
AI agents call get_spans_summary to retrieve information from Respan MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure data retrieval operation that queries existing logs and spans to compute and return aggregated statistics. It has no side effects, does not modify data, does not execute code, and does not commit financial transactions. While it retrieves cost information, it does not move money or create financial obligations—it only reads historical cost data for informational purposes.
From the tool's definition Tool description states it 'Retrieve[s] aggregated summary statistics' and is 'Useful for getting quick insights into your LLM usage without fetching all individual spans.' Parameters include only temporal filters (start_time, end_time) and optional…
Attacks that exploit this kind of access
Retrieve aggregated summary statistics for log spans. Returns total_count, total_cost, total_tokens, avg_latency etc. Useful for getting quick insights into your LLM usage without fetching all individual spans. PARAMETERS: - start_time: Start time in ISO 8601 format (required) - end_time: End time in ISO 8601 format (required) - filters: Optional object of server-side filters in backend format: { field_name: { operator, value } } RESPONSE FIELDS: - total_cost: Total cost in USD for all filtered spans - total_tokens: Total tokens (prompt + completion) - number_of_requests: Total number of requests matching filters - scores: Aggregated score summaries grouped by evaluator_id EXAMPLE: {. It is categorised as a Read tool in the Respan MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Respan MCP Server MCP server in PolicyLayer and add a rule for get_spans_summary: 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 Respan MCP Server. Nothing to install.
get_spans_summary 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 get_spans_summary 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 get_spans_summary. 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.
get_spans_summary is provided by the Respan MCP Server MCP server (respanai/respan-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 →