Skip to content

Add fak (agent tool firewall) to Tools #38

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
anthony-chaudhary wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add fak (agent tool firewall) to Tools #38

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,6 +48,7 @@ Contributions are always welcome. Please read the [Contribution Guidelines](CONT
- [MCP-Shield](https://github.com/riseandignite/mcp-shield) - Scans your installed MCP servers and detects vulnerabilities like tool poisoning attacks, exfiltration channels and cross-origin escalations.
- [mcp-injection-experiments](https://github.com/invariantlabs-ai/mcp-injection-experiments/tree/main) - MCP Tool Poisoning Experiments
- [MCP Guardian](https://github.com/eqtylab/mcp-guardian) - Manages your LLM assistant's access to MCP servers, handing you realtime control of your LLM's activity.
- [fak](https://github.com/anthony-chaudhary/fak) - Agent tool firewall that fronts an MCP server: a default-deny capability gate adjudicates every tool call before it runs (irreversible actions fail closed), and suspicious tool results are quarantined out of the model’s context to contain Tool Poisoning / Memory Poisoning. Exposes five `fak_*` adjudication tools to any MCP client; single static Go binary, Apache-2.0.

## Articles and Blog Posts -

Expand Down