get_performance_summary
Retrieve time-series performance summary data in 15-minute intervals in JSON format for trend analysis and historical comparison. Returns data aggregated in 15-minute time buckets showing requests, errors, and 95th percentile response times.
This record as markdown: /tools/5hahil-tideways-mcp-server/get-performance-summary.md
What get_performance_summary does on Tideways MCP Server
AI agents call get_performance_summary to retrieve information from Tideways MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_performance_summary is rated Low
This tool retrieves and aggregates historical performance metrics (requests, errors, response times) from Tideways monitoring data. It performs a read-only query operation with no side effects, no data mutation, and no external command execution. The data returned is for analysis and trend comparison purposes only. This is a straightforward monitoring data retrieval use case with minimal risk.
From the tool's definition Tool description states 'Retrieve time-series performance summary data' and 'Returns data aggregated' - uses retrieve/return language indicating data querying with no modification.
Attacks that exploit this kind of access
The rule that runs get_performance_summary safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tideways MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_performance_summary, this is the rule to start with:
get_performance_summary 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 Tideways MCP Server, apply this rule, and every get_performance_summary call is checked against it from then on.
Questions about get_performance_summary
Retrieve time-series performance summary data in 15-minute intervals in JSON format for trend analysis and historical comparison. Returns data aggregated in 15-minute time buckets showing requests, errors, and 95th percentile response times. It is categorised as a Read tool in the Tideways MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Tideways MCP Server MCP server in PolicyLayer and add a rule for get_performance_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 Tideways MCP Server. Nothing to install.
get_performance_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_performance_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_performance_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_performance_summary is provided by the Tideways MCP Server MCP server (5hahil/tideways-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tideways MCP Server, and thousands of servers like it.
This server
Across the catalogue