# 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).

Agent View of the PolicyLayer registry record for `get_performance_metrics`. HTML page: https://policylayer.com/tools/5hahil-tideways-mcp-server/get-performance-metrics

## Facts

- Tool: `get_performance_metrics`
- Server: Tideways MCP Server (`5hahil/tideways-mcp-server`) — https://policylayer.com/tools/5hahil-tideways-mcp-server.md
- Homepage: https://github.com/5hahiL/tideways-mcp-server
- Risk category: Read (Low risk)
- Registry record: grade A, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_performance_metrics",
    "arguments": {}
  }
}
```

## 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 own definition: "Tool name 'get_performance_metrics' and description states 'Retrieve aggregate performance metrics' — uses retrieval language with no modification, deletion, or execution semantics."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Tideways MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_performance_metrics": {}
  }
}
```

## Other tools on Tideways MCP Server (4)

- `get_historical_data` — Read — https://policylayer.com/tools/5hahil-tideways-mcp-server/get-historical-data.md
- `get_issues` — Read — https://policylayer.com/tools/5hahil-tideways-mcp-server/get-issues.md
- `get_performance_summary` — Read — https://policylayer.com/tools/5hahil-tideways-mcp-server/get-performance-summary.md
- `get_traces` — Read — https://policylayer.com/tools/5hahil-tideways-mcp-server/get-traces.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=5hahil-tideways-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/5hahil-tideways-mcp-server