get_glp_audit_log_v2_detail

What get_glp_audit_log_v2_detail does on API-Central

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

Why get_glp_audit_log_v2_detail is rated Low

This tool retrieves historical audit log data for the GreenLake Platform (GLP). It performs a read-only query of existing audit entries to fetch detailed information. There are no side effects, data modifications, deletions, or external operations triggered. The blast radius of misuse is minimal—an attacker could view audit logs they shouldn't access, but cannot modify, delete, or execute actions through this tool.

From the tool's definition Tool name contains 'get_' prefix and description uses 'Fetch' - both indicate retrieval operation. Description specifies reading audit-log entries with no modification or deletion mentioned.

The rule that runs get_glp_audit_log_v2_detail safely

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

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

Questions about get_glp_audit_log_v2_detail