Rohlik Grocery Shopping: why it is not safe to use
Warn: this skill can change a live Rohlik cart without an explicit confirmation step and accesses sensitive grocery account data via stored credentials.
What we found
Our review did not find hidden instructions, hardcoded secrets, obfuscated code, or undisclosed third-party destinations. The inspected code appears to talk to the user-selected Rohlik Group endpoint for its stated shopping functions.
The main concern is how the skill operates on a live grocery account. It can add items to a cart and remove items from a cart, and the inspected handlers do not show an explicit confirmation step before those account changes are made. That raises the chance of unintended actions if a request is ambiguous or triggered in error.
We also found that the skill reads `ROHLIK_USERNAME` and `ROHLIK_PASSWORD` from environment variables and can access order history, cart, delivery, and account data for the connected account. This appears limited to the user-chosen Rohlik account, but it still involves sensitive personal commerce data.
What to do instead
Use this skill only if you are comfortable connecting a real Rohlik account and granting access to cart and order information. Prefer setups that require a clear user confirmation before any cart modification. If possible, use a dedicated account with minimal saved personal data, review cart changes before checkout, and avoid sharing credentials beyond the environment where you control them.
Source: https://github.com/tomaspavlin/rohlik-mcp
We report what our security review found at the time we checked, with the goal of keeping people safe. Projects change; if a maintainer has since fixed this, we are glad to recheck it. Email hello@agentpod.com.