# get_historical_data

Retrieve historical performance data in JSON format for a specific date with configurable granularity. Analyze daily, weekly, or monthly performance trends, transaction reports, and time-series metrics.

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

## Facts

- Tool: `get_historical_data`
- 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_historical_data",
    "arguments": {}
  }
}
```

## Why get_historical_data is rated Low

The tool performs data retrieval and analysis of existing performance metrics from Tideways without any capability to modify, delete, or execute operations. It is a read-only query operation against historical monitoring data. The configurable granularity refers to query parameters (time periods) not execution capabilities. This poses minimal risk if an AI agent misuses it.

From the tool's own definition: "Tool description states 'Retrieve historical performance data' and 'Analyze daily, weekly, or monthly performance trends' — purely retrieval operations with no modification, deletion, or execution of external code."

## Use case

AI agents call get_historical_data 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_historical_data": {}
  }
}
```

## Other tools on Tideways MCP Server (4)

- `get_issues` — Read — https://policylayer.com/tools/5hahil-tideways-mcp-server/get-issues.md
- `get_performance_metrics` — Read — https://policylayer.com/tools/5hahil-tideways-mcp-server/get-performance-metrics.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