prowler-test-mcp

Use an in-memory client: `async with Client(mcp_root_server)` and call tools through it. This is required because pydantic Field defaults on tool parameters only resolve through the FastMCP wrapper; direct calls leave omitted arguments as truthy FieldInfo objects.

Use the mock_api_client fixture, which patches the ProwlerAPIClient singleton's httpx transport in place. Never construct a new ProwlerAPIClient, because tool instances captured the singleton by reference at import time.

Calling a tool method directly with an omitted argument leaves it as a raw FieldInfo object, which is truthy, so conditions like `if email:` build filters from the FieldInfo repr. Always drive tools through the in-memory FastMCP client or pass every argument explicitly.

No. Clearing the registry orphans every registered tool on an instance holding a real httpx.AsyncClient. Use the isolated_api_client fixture when you genuinely need a fresh instance for construction or identity tests.

Tools are built at import time and construction failures are swallowed, so stripping the PROWLER_API_KEY environment variable silently drops the whole prowler_ namespace to zero tools. The key is pinned in pytest env configuration and must not be removed.

Register the same route multiple times on MockRouter to return a response sequence, such as executing then completed; the last response repeats. Then call poll_task_until_complete with poll_interval=0 and assert the terminal state.