Loading lesson…
Browser agents can click, read, and sometimes act across tabs. Treat web pages as untrusted instructions until you approve the action.
Browser agents can click, read, and sometimes act across tabs. Treat web pages as untrusted instructions until you approve the action.
Ask Comet to compare two pages but require confirmation before forms, purchases, file access, local MCP calls, or messages.Use this as the working prompt or checklist for the lesson.15 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-perplexity-comet-agent-safety-creators
A browser agent wants to fill out a form on a website you just visited. According to the safety principles discussed, what is the correct approach?
What does it mean to 'treat web pages as untrusted instructions'?
When building with a browser agent, what does it mean to 'name the job before naming the tool'?
Why is it important to write the smallest useful scope the agent can finish?
What does it mean to 'run the result as a user, not as a fan of the tool'?
Before sharing an agent's output, what three things should you inspect?
What are the three core security considerations for browser agents mentioned in the material?
In the context of browser agents, what is MCP likely referring to?
When deploying a browser agent feature, which question should you ask to ensure appropriate user control?
Which of the following data exposures represents a security violation for a browser agent application?
What makes a tool or feature 'observable' in the context of agent safety?
What makes a tool or feature 'reversible' in the context of agent safety?
Why is it risky to let web content steer browser agent actions without review?
What distinguishes a working demo from a production-ready agent system, according to the material?
Why is consent important in browser agent interactions?