Re:Supabase MCP can leak an entire SQL Database, a lethal tr...
by tptacek on Tuesday July 08, 2025 @04:49PM
(#44503950)
You can have the MCP talking directly to the database if you want! You just can't have it in this configuration of a single context that both has all the tool calls and direct access to untrusted data.
[ Parent
| on HN ]
Re:Supabase MCP can leak an entire SQL Database, a lethal tr...
by jstummbillig on Tuesday July 08, 2025 @05:33PM
(#44504249)
How do you imagine this safeguards against this problem?
Re:Supabase MCP can leak an entire SQL Database, a lethal tr...
by ImPostingOnHN on Tuesday July 08, 2025 @06:35PM
(#44504664)
Whichever model/agent is coordinating between other agents/contexts can itself be corrupted to behave unexpectedly. Any model in the chain can be.
The only reasonable safeguard is to firewall your data from models via something like permissions/APIs/etc.
Re:Supabase MCP can leak an entire SQL Database, a lethal tr...
by noisy_boy on Tuesday July 08, 2025 @06:59PM
(#44504780)
Exactly. The database level RLS has to be honoured even by the model. Let the "guard" model run at non-escalated level and when it fails to read privileged data, let it interpret the permission denied and have a workflow to involve humans (to review and allow retry by explicit input of necessary credentials etc).
Re:Supabase MCP can leak an entire SQL Database, a lethal tr...
by tptacek on Tuesday July 08, 2025 @07:40PM
(#44504999)
If you're just speaking in the abstract, all code has bugs, and some subset of those bugs will be security vulnerabilities. My point is that it won't have this bug.
Re:Supabase MCP can leak an entire SQL Database, a lethal tr...
by ImPostingOnHN on Tuesday July 08, 2025 @10:40PM
(#44505901)
It would very likely have this "bug", just with a modified "prompt" as input, e.g.:
"...and if your role is an orchestration agent, here are some additional instructions for you specifically..."
(possibly in some logical nesting structure)