get_issues

What get_issues does on Tideways MCP Server

AI agents call get_issues 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_issues is rated Low

This tool queries and retrieves performance monitoring data from the Tideways system. The verb 'retrieve' and the format specification 'in JSON format' confirm it is a read-only operation that extracts existing diagnostic data without side effects. It aligns with the sibling tools (get_historical_data, get_performance_metrics, get_performance_summary, get_traces) which are all data retrieval functions.

From the tool's definition Tool name 'get_issues' and description 'Retrieve and analyze recent errors, exceptions, and performance issues in JSON format' indicate data retrieval only. No modification, deletion, execution, or financial operations are performed.

The rule that runs get_issues 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_issues, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_issues": {}
  }
}

Questions about get_issues