get_performance_metrics
Retrieve aggregate performance metrics and system-wide statistics in JSON format. Use for monitoring overall application health, trends, and high-level performance overview (use get_traces for detailed individual request analysis).
This record as markdown: /tools/5hahil-tideways-mcp-server/get-performance-metrics.md
What get_performance_metrics does on Tideways MCP Server
AI agents call get_performance_metrics 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_metrics is rated Low
The tool retrieves and queries performance data for monitoring purposes with no side effects. It aggregates existing metrics without creating, modifying, deleting, or executing operations. This is a straightforward Read operation with minimal risk if misused by an AI agent — worst case is excessive API calls or information disclosure of already-accessible monitoring data.
From the tool's definition Tool name 'get_performance_metrics' and description states 'Retrieve aggregate performance metrics' — uses retrieval language with no modification, deletion, or execution semantics.
Attacks that exploit this kind of access
The rule that runs get_performance_metrics 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_metrics, this is the rule to start with:
get_performance_metrics 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_metrics call is checked against it from then on.
Questions about get_performance_metrics
Retrieve aggregate performance metrics and system-wide statistics in JSON format. Use for monitoring overall application health, trends, and high-level performance overview (use get_traces for detailed individual request analysis). 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_metrics: 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_metrics 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_metrics 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_metrics. 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_metrics 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