get_skip_scan_status

What get_skip_scan_status does on Mcpg

AI agents call get_skip_scan_status to retrieve information from Mcpg without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_skip_scan_status is rated Low

The tool retrieves status information about skip scan optimization in PostgreSQL. The 'get_' prefix and '_status' suffix indicate a read operation that queries existing state without modifying or executing anything. While the description is empty, the naming convention is strong evidence of a read operation.

From the tool's definition Tool name 'get_skip_scan_status' follows the 'get_*' pattern which is characteristic of retrieval operations. It queries the status of skip scans, a PostgreSQL query optimization technique, with no indication of modification or execution.

The rule that runs get_skip_scan_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcpg, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_skip_scan_status, this is the rule to start with:

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

Questions about get_skip_scan_status