Inspiration
As MCP proliferate users need protection. Not friction, not prevention but protection.
What it does
It monitors WebMCP tool and API calls and based on policy that the admin sets, protects the user and the enterprise.
How we built it
It is an extension service that is focused on observing and protecting webMCP calls
Challenges we ran into
Protecting the extension while it protects the users.
Accomplishments that we're proud of
We have two methods to block in the extension
- Block or allow the tool from registering if its found malicious or based on a fingerprint
- Block or allow the tool based on policy that is based on context such as "DLP" context, but doesn't prevent tool registration.
What we learned
Browser security is where everyone works and if you don't have visibility into he browser-runtime you don't have visibility where people work.
What's next for Browser MCP Firewall/Protection
Plan to launch as a release product through via the capital connect program at nvidia.
Log in or sign up for Devpost to join the conversation.