Forge documentation
Runtime concepts

Tools and approval

Tools and approval concepts mapped to actual Forge source packages.

A tool definition describes its name, arguments and tier; an executor performs the operation. Validate arguments before execution, then enforce both capability authorization and approval. Correlate every result with the original tool-call ID. AutoApprove is an actual built-in policy, not a security boundary.

Implementation references

The references below are the Rust implementation. They include manifest versions, features, source hashes, and declarations.

Other languages

Use the language-specific package catalog for TypeScript, Python, Go, Swift and Kotlin. Similar responsibilities do not imply the same types, defaults, targets or deployed capabilities.

Validation

Read the exact package boundary and selected feature conditions. Run the relevant library tests and the applicable conformance fixtures before making a release claim. Source documentation and generated inventories do not replace runtime verification.

On this page