cdp_get_orchestration_status_log

What cdp_get_orchestration_status_log does on CDP MCP Server

AI agents call cdp_get_orchestration_status_log to retrieve information from CDP 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 cdp_get_orchestration_status_log is rated Low

The tool appears designed to fetch status logs for orchestration processes, a classic read operation. No description was provided, which slightly lowers confidence, but the 'get_' prefix and '_status_log' suffix strongly suggest retrieval of historical log data without modification. Blast radius is minimal since reading logs cannot alter system state or cause financial harm.

From the tool's definition Tool name 'cdp_get_orchestration_status_log' contains 'get', which indicates data retrieval with no side effects. The naming convention follows a read-only query pattern typical of observability/logging endpoints.

The rule that runs cdp_get_orchestration_status_log safely

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

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

Questions about cdp_get_orchestration_status_log