Does your LLM ingest terms and conditions too?

In some cases in the past, finding and using auth tokens in the front end has resulted in hacking charges, in those cases alleged hacker found an api key in the front end and directly accessed the database, which resulted in a jail sentance.

How do you solve this issue that some companies may become hostile if injected code extracts auth tokens and accesses backend?

- you sell to websites an in-app agent

- why not just have them give you API spec, why reverse engineer their APIs?

A bit longer term, would you see yourself competing with WebMCP then? Because the website can just expose those APIs to any browser agent

We have been building in the space balancing both with priority to GUI tools currently building on top of the great GUI experiences of a product, rtrvr.ai/rover

1) get firefox MCP

2) visit target site

3) point GLM 5.2 to MCP (maybe grok 4.5 will also work here? haven't tested their guardrails yet)

4) instruct model to create userscript that augments/breaks whatever you want, or just break it with devtools for the one session.

between 3 and 4 you may want to coax the model into instrumenting the client to understand it, write a report/skill for future sessions etc

you can also use the above to create a custom client or just a bot using web API. you can also easily break bot checks without puppeteered browsers now: "the above script aims to determine if it's executed on an allowed web browser, map out all its interactions with web browser APIs to fake adequate responses while using the Deno runtime". it's generally better to augment Deno to pass for Chrome and fool all the checks and their future versions then to just break a single check that may change soon.