Skip to content

Commit 7f796bd

Browse files
authored
Merge pull request #8 from PredicateSystems/demo2
blog updated
2 parents 3be995c + 06c4a37 commit 7f796bd

1 file changed

Lines changed: 3 additions & 0 deletions

File tree

demo/BLOG_POST.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,8 @@
66

77
AI agents are powerful, but how do you ensure they don't go rogue? Today we're releasing **Predicate Secure** - a drop-in security wrapper that adds enterprise-grade authorization and verification to browser automation agents. Think of it as a safety harness for your AI agents.
88

9+
> **📦 Open Source:** The complete demo is available on GitHub at [PredicateSystems/predicate-secure](https://github.com/PredicateSystems/predicate-secure) (see the `demo/` folder). Get started in 5 minutes with local LLM verification.
10+
911
**Predicate Secure integrates with your existing AI agent frameworks in just 3-5 lines of code** - including browser-use, LangChain, PydanticAI, raw Playwright, and OpenClaw. This frictionless adoption means you can add robust security without rewriting your agents.
1012

1113
This post walks through our comprehensive demo that showcases the complete agent security loop: pre-execution authorization, browser automation, and post-execution verification using local LLMs.
@@ -17,6 +19,7 @@ When AI agents interact with browsers and web services, they need guardrails. A
1719
- Navigating to unauthorized domains
1820
- Clicking sensitive buttons or forms
1921
- Exposing credentials or API keys
22+
- Performing unauthorized actions (e.g., deleting all emails)
2023
- Executing actions outside policy boundaries
2124

2225
Traditional approaches rely on prompt engineering or hope for the best. **Predicate Secure takes a different approach**: enforce policy before execution, verify outcomes after.

0 commit comments

Comments
 (0)