coverage.acquire_missing

What coverage.acquire_missing does on Visionmcp

AI agents invoke coverage.acquire_missing to trigger actions in Visionmcp. 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 coverage.acquire_missing is rated High

This tool initiates a search operation and can issue capture requests, making it an Execute-class tool rather than a simple Read operation. The search is described as 'bounded governed' suggesting controlled scope, which limits severity to medium rather than high. Without evidence of data deletion, modification, or financial impact, Execute is the appropriate category.

From the tool's definition Tool description states 'Execute a bounded governed search for gaps, or issue precise capture requests.' The verb 'Execute' combined with 'search' and 'capture requests' indicates the tool triggers operations whose effects depend on arguments provided.

The rule that runs coverage.acquire_missing safely

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

{
  "version": "1",
  "default": "deny",
  "tools": {
    "coverage.acquire_missing": {
      "limits": [
        {
          "counter": "coverage.acquire_missing_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about coverage.acquire_missing