Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

Hi, I’ve signed the CLA. The fix ensures reference list tools handle mixed entry types safely.
Please review when convenient. Thanks!

Hi @google/mergers and @dandye
I’ve signed the CLA and all checks have passed
This PR fixes issue #168 by handling mixed entry types (string, dict, object) safely in reference list management.
Requesting your review at the earliest convenience. Thanks a lot for your time

Hi, I've tested and can confirm that the issue has been resolved. Thank you

Hi @Adriana1969 and @alberto-mate team,

The reporter has confirmed that this PR #175 resolves the issue successfully ✅.
All checks have passed and CLA is signed.

Kindly requesting the maintainers to review and merge the PR at the earliest convenience. Thanks a lot

Hi @google/mergers @dandye @emeryray2002 @alberto-mate,

The original issue reporter @Adriana1969 has confirmed that the issue is resolved by PR #175.
All checks have passed and the CLA is signed.

Kindly requesting your review and approval so this fix can be merged at the earliest convenience.
Thank you very much for your attention!

@MRADULTRIPATHI Thanks for this change.

I was still running into the str has no attribute value issue with the proposed changes. It turns out that the get_reference_list method in ChronicleClient expects a StrEnum rather than a plain string, which was causing the error.

I’ve updated the view handling in addition to the existing changes.

I’ll update get_reference_list separately, but in the meantime these PR changes should work.

Test Plan

Tested Following using Cline extension in VS Code and able to successfully utilize get_reference_list tool from secops-mcp.

1. Get reference list details

2. Get reference list details with entries

Hi @dandye @emeryray2002,

The PR #175 is now fully ready:

• Approved ✅ by collaborator @mihrivala-crestdata
• All checks have passed ✅
• No conflicts with base branch

Kindly requesting your review and merge at the earliest convenience 🙏
Thanks a lot for helping close this out!

Hi @mihirvala-crestdata,

Thank you so much for your support, updates, and for approving this PR.
Your additional fixes and the test plan were really helpful in making sure everything works correctly.

If I may ask — do you have an idea of how much time it might take for this PR to get merged?
Thanks again for your time and guidance!

Hi @google/mergers,

The PR #175 is now:

• Approved
• All checks passed
• No conflicts with base branch

It is fully ready to merge. Kindly requesting your assistance to complete the merge