Error using reference list management tools: 'str' object has no attribute 'value'

[Adriana1969]

Encountered a TypeError when attempting to use the reference list management tools on the SecOps MCP server. The specific error message is: 'str' object has no attribute 'value'. This error occurs consistently across different tools related to reference list management.

[MRADULTRIPATHI]

Hi @Adriana1969 and @dandye

I’ve submitted PR [#175]
that addresses this issue by handling mixed entry types safely in reference list management.
All checks have passed ✅ and CLA is signed.

Could you please take a look and confirm if this resolves the problem on your side? Thanks

[Adriana1969]

Hi, I have tested the PR and now it's working fine. Thank you. Regards Adriana El mar, 2 sept 2025 a las 23:52, MRADUL TRIPATHI ***@***.***>) escribió:

…

*MRADULTRIPATHI* left a comment (google/mcp-security#168) <#168 (comment)> Hi @Adriana1969 <https://github.com/Adriana1969>, I’ve submitted PR #175 <https://github.com/google/mcp-security/pull/175?utm_source=chatgpt.com> that addresses this issue by handling mixed entry types safely in reference list management. All checks have passed ✅ and CLA is signed. Could you please take a look and confirm if this resolves the problem on your side? Thanks — Reply to this email directly, view it on GitHub <#168 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A57SWDRT2HY7UZSQDZXJIMD3QYGRLAVCNFSM6AAAAACFJ4K3VWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTENBWHEYTGMBWGI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[MRADULTRIPATHI]

Hi @Adriana1969, thanks a lot for confirming that the fix works
Since the reporter has verified the solution and all checks have passed ✅ (with CLA signed), I’d kindly request the maintainers to please review and merge PR [#175] at the earliest convenience.

Thanks again for your time and support!

[MRADULTRIPATHI]

Hi @dandye,@emeryray2002

All checks have passed ✅, CLA is signed, and the @Adriana1969 reporter has confirmed that the fix resolves the issue.
However, the PR (#175) is still pending review and merge.

Could you please help by reviewing or guiding it through the merge process?
Your support would be greatly appreciated

[MRADULTRIPATHI]

Hi @dandye @emeryray2002 @navnongooglecom,

Kind follow-up 🙏 The reporter @Adriana1969 has verified the fix, all checks are green ✅, and the CLA is signed.
PR #175 is pending only on maintainer review/merge.

Could you please take a look or help route it to the right reviewer? Thanks so much!