fix: use investigate/v2 API path for domain tools

[ymeloch]

Summary

• Fixes the get_domain_categorization and investigate_domain tools, which called non-existent security/v1/domains/{domain}/... routes and always failed with 404 "no Route matched".
• Switches both tools to the correct Cisco Secure Access Investigate API scope (investigate/v2) and path order (resource before domain).
• URL-encodes the domain argument before interpolating it into the request path, and removes the now-unused SECURITY_SCOPE constant.

Closes #12

Details

Before:

await client.get(SECURITY_SCOPE, f"domains/{domain}/categorization")  # security/v1 -> 404
await client.get(SECURITY_SCOPE, f"domains/{domain}/risk-score")      # security/v1 -> 404

After:

safe_domain = quote(domain, safe="")
await client.get(INVESTIGATE_SCOPE, f"domains/categorization/{safe_domain}")
await client.get(INVESTIGATE_SCOPE, f"domains/risk-score/{safe_domain}")

Endpoints now match the documented Investigate API:

• GET https://api.sse.cisco.com/investigate/v2/domains/categorization/{domain}
• GET https://api.sse.cisco.com/investigate/v2/domains/risk-score/{domain}

See the Cisco DevNet Investigate API overview and API changelog.

Test plan

• get_domain_categorization("example.com") returns {"example.com": {"status": 0, "content_categories": ["54", "188"]}} against a live tenant (previously 404).
• investigate_domain returns a risk-score payload for a domain (same scope/path-order fix; requires Investigate access tier that exposes risk-score).

Made with Cursor