get_diagnostics

What get_diagnostics does on Ludus FastMCP

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

Why get_diagnostics is rated Low

This tool retrieves system diagnostic data without altering state, executing code, or triggering external operations. The 'get' prefix and passive retrieval nature place it squarely in the Read category. Severity is low because diagnostic data typically contains no sensitive information that would grant privilege escalation or unauthorized access, and misuse poses minimal risk to the system.

From the tool's definition Tool name 'get_diagnostics' and description 'Get system diagnostics' indicate retrieval of diagnostic information with no modification or execution capability.

The rule that runs get_diagnostics safely

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

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

Questions about get_diagnostics