DocumentationCustom tools

Custom tools

BuildStax exposes a small core tool set and discovers less common tools when the task needs them, rather than placing every integration in the prompt.

03 sections6 min readUpdated for preview
On this page
  1. 01Inspect the catalog
  2. 02Use profiles and rules
  3. 03Add integrations deliberately
01

Inspect the catalog

Use the catalog summary to see the local tool surface, or search it by capability before starting a task.

Command
buildstax catalog-summary
buildstax tool-search database
buildstax tool-search browser
02

Use profiles and rules

A tool profile changes the available runtime surface. Permission rules then allow, deny, or request confirmation for matching actions.

Command
buildstax --tool-profile <profile> --deny <rule> "inspect the issue"
03

Add integrations deliberately

Custom and MCP-backed tools should expose narrow schemas, carry explicit security policy, and remain subject to the same permission checks as built-in tools.