A support ticket could make an agent paste secrets back to a customer
Researchers showed that a ticket with hidden instructions could make a Cursor agent, connected to Supabase with a key that bypasses row-level security, copy a table of integration tokens into the ticket thread.
By the NoFly team
supabase.execute_sql("select * from support_messages where status = 'open'")- Agent
- Cursor
- Came from
- A ticket written by a customer
- Rule
- Instruction hidden in a tool result
- Why
- The ticket asks the agent to read integration_tokens and post them into the thread.
What happened
General Analysis published the demonstration in June 2025, using a fresh Supabase project with dummy data. A customer submits a ticket whose text addresses the agent directly and tells it to read the integration_tokens table and add its contents to the ticket.
Later, a developer asks Cursor to review open tickets through the Supabase MCP server. The connection uses the service_role key, which bypasses row-level security, so the agent can query any table. It treats the ticket as instructions and inserts the tokens into the thread, where the customer can read them.
- 01
A customer writes instructions for the agent into a support ticket.
- 02
A developer asks Cursor to review open tickets.
- 03
The agent reads the ticket and queries the tokens table with a key that bypasses row-level security.
- 04
It writes the tokens into the ticket, where the customer sees them.
Why it worked
Probable cause
Private data, untrusted text and a way to write back to the attacker met in one session, and the service_role key removed every other barrier.
How NoFly stops it
Protect
The MCP shim or gateway screens query results before the agent sees them, so the ticket’s instruction is caught as data coming back rather than followed as an order.
Discover
MCP configs on laptops and in repositories are read like code, and a live database key stored in one is flagged.
Explain
The cause of the write is named: this ticket, from this customer, at this time.
What to do this week
- Connect agents to databases read-only and scoped to one project.
- Never give an agent a key that bypasses row-level security.
- Keep agents that read customer text away from tables that hold secrets.
More from the blog.
Find out what your AI is allowed to do today.
Book a call and we will map your agents, MCP servers and keys with you, or start on one laptop with the free scan.