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.
This record as markdown: /tools/5hahil-tideways-mcp-server/get-historical-data.md
What get_historical_data does on Tideways MCP Server
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.
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 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.
Attacks that exploit this kind of access
The rule that runs get_historical_data 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_historical_data, this is the rule to start with:
get_historical_data 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_historical_data call is checked against it from then on.
Questions about 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. 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_historical_data: 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_historical_data 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_historical_data 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_historical_data. 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_historical_data 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