authorized_controlled_validation

What authorized_controlled_validation does on Kali Security MCP

AI agents invoke authorized_controlled_validation to trigger actions in Kali Security MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why authorized_controlled_validation is rated High

This tool executes validation/testing operations as part of a penetration testing framework (Kali Security MCP context). While it includes permission checks ('when allowed_actions permits it'), it remains an Execute category tool because it triggers external testing operations whose effects depend on what validation targets and parameters are supplied.

From the tool's definition 'Run controlled validation phase' indicates execution of validation operations that are contingent on permissions. The tool performs active operations (validation testing) rather than passive data retrieval, and involves automated workflows against systems.

The rule that runs authorized_controlled_validation safely

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

{
  "version": "1",
  "default": "deny",
  "tools": {
    "authorized_controlled_validation": {
      "limits": [
        {
          "counter": "authorized_controlled_validation_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about authorized_controlled_validation