HackerTrans
TopNewTrendsCommentsPastAskShowJobs

rexpository

no profile record

Submissions

[untitled]

1 points·by rexpository·4 bulan yang lalu·0 comments

[untitled]

1 points·by rexpository·10 bulan yang lalu·0 comments

[untitled]

1 points·by rexpository·12 bulan yang lalu·0 comments

Ship like a team of 5 with Claude Code

every.to
2 points·by rexpository·12 bulan yang lalu·0 comments

[untitled]

1 points·by rexpository·12 bulan yang lalu·0 comments

[untitled]

1 points·by rexpository·12 bulan yang lalu·0 comments

[untitled]

1 points·by rexpository·12 bulan yang lalu·0 comments

[untitled]

1 points·by rexpository·12 bulan yang lalu·0 comments

[untitled]

1 points·by rexpository·tahun lalu·0 comments

Exploiting Partial Compliance: The Redact-and-Recover Jailbreak

generalanalysis.com
5 points·by rexpository·tahun lalu·0 comments

Supabase MCP can leak your entire SQL database

generalanalysis.com
848 points·by rexpository·tahun lalu·470 comments

The LLM Jailbreaking Bible: Code Implementation and Overview

generalanalysis.com
9 points·by rexpository·tahun lalu·2 comments

comments

rexpository
·12 bulan yang lalu·discuss
In Claude desktop, you can see that the iMessage integration is authored/developed by Anthropic.https://imgur.com/a/RWDvDZh
rexpository
·12 bulan yang lalu·discuss
General Analysis has released an open source MCP guard to secure your MCP clients against prompt injection attacks like these. https://generalanalysis.com/blog/mcpguard
rexpository
·12 bulan yang lalu·discuss
General Analysis has released an open source MCP guard to secure your MCP clients against prompt injection attacks like these. https://generalanalysis.com/blog/mcpguard
rexpository
·tahun lalu·discuss
I broadly agree that "MCP-level" patches alone won't eliminate prompt-injection risk. Latest research also shows we can make real progress by enforcing security above the MCP layer, exactly as you suggest [1]. DeepMind's CaMeL architecture is a good reference model: it surrounds the LLM with a capability-based "sandbox" that (1) tracks the provenance of every value, and (2) blocks any tool call whose arguments originate from untrusted data, unless an explicit policy grants permission.

[1] https://arxiv.org/pdf/2503.18813