mirror of
https://github.com/block/goose.git
synced 2026-05-05 07:09:34 +00:00
Some checks failed
Canary / Prepare Version (push) Failing after 3s
Canary / bundle-desktop (push) Has been skipped
Canary / bundle-desktop-intel (push) Has been skipped
Canary / bundle-desktop-linux (push) Has been skipped
Canary / bundle-desktop-windows (push) Has been skipped
Canary / build-cli (push) Has been skipped
Canary / Upload Install Script (push) Has been skipped
Canary / Release (push) Has been skipped
Unused Dependencies / machete (push) Has been skipped
CI / changes (push) Failing after 3s
Deploy Documentation / deploy (push) Failing after 4s
Live Provider Tests / check-fork (push) Successful in 2s
Publish Ask AI Bot Docker Image / docker (push) Failing after 5s
Publish Docker Image / docker (push) Failing after 3s
Scorecard supply-chain security / Scorecard analysis (push) Has been skipped
CI / Check Rust Code Format (push) Has been skipped
CI / Build and Test Rust Project (push) Has been skipped
CI / Lint Rust Code (push) Has been skipped
CI / Check OpenAPI Schema is Up-to-Date (push) Has been skipped
Live Provider Tests / changes (push) Failing after 3s
Live Provider Tests / Build Binary (push) Has been skipped
Live Provider Tests / Smoke Tests (Code Execution) (push) Has been skipped
Live Provider Tests / Smoke Tests (push) Has been skipped
Live Provider Tests / Compaction Tests (push) Has been skipped
Live Provider Tests / goose server HTTP integration tests (push) Has been skipped
CI / Test and Lint Electron Desktop App (push) Has been cancelled
55 lines
2.1 KiB
Text
55 lines
2.1 KiB
Text
---
|
|
title: Staying Safe with goose
|
|
hide_title: true
|
|
description: Keep your goose workflows safe with built-in security features and best practices
|
|
---
|
|
|
|
import Card from '@site/src/components/Card';
|
|
import styles from '@site/src/components/Card/styles.module.css';
|
|
|
|
<h1 className={styles.pageTitle}>Staying Safe with goose</h1>
|
|
<p className={styles.pageDescription}>
|
|
Understanding security risks and following best practices can help you secure your workflows with goose.
|
|
</p>
|
|
|
|
<div className={styles.categorySection}>
|
|
<h2 className={styles.categoryTitle}>📚 Documentation & Guides</h2>
|
|
<div className={styles.cardGrid}>
|
|
<Card
|
|
title="Adversary Mode"
|
|
description="An independent agent reviewer that silently watches tool calls to protect you in case the agent goes rogue."
|
|
link="/docs/guides/security/adversary-mode"
|
|
/>
|
|
<Card
|
|
title="Prompt Injection Detection"
|
|
description="Detect and prevent potentially harmful commands before they run."
|
|
link="/docs/guides/security/prompt-injection-detection"
|
|
/>
|
|
<Card
|
|
title="Classification API Specification"
|
|
description="API specification for self-hosting ML-based prompt injection detection endpoints."
|
|
link="/docs/guides/security/classification-api-spec"
|
|
/>
|
|
<Card
|
|
title="macOS Sandbox for goose Desktop"
|
|
description="Control file access, network connections, and process restrictions for goose Desktop using Apple's sandbox technology."
|
|
link="/docs/guides/sandbox"
|
|
/>
|
|
</div>
|
|
</div>
|
|
|
|
<div className={styles.categorySection}>
|
|
<h2 className={styles.categoryTitle}>📝 Featured Blog Posts</h2>
|
|
<div className={styles.cardGrid}>
|
|
<Card
|
|
title="How to Determine If An MCP Server Is Safe"
|
|
description="Before you plug your agent into just any MCP server, here's how to check if it's actually safe."
|
|
link="/blog/2025/03/26/mcp-security"
|
|
/>
|
|
<Card
|
|
title="Securing the Model Context Protocol"
|
|
description="Building secure and capable AI integrations with Model Context Protocol (MCP) at Block."
|
|
link="/blog/2025/03/31/securing-mcp"
|
|
/>
|
|
</div>
|
|
</div>
|