tools/list is the authoritative tool reference for the current actor. Forge
builds each definition from the same capability registry used by the REST API
and CLI.
Each advertised tool contains:
inputSchema; do not maintain a
separate permissive schema. Tool schemas reject unknown properties.
Discovery tools
Investigation tools
Policy tools
Governance tools
MCP approval tools
Assurance tools
Administration tools
Calling a tool
Use the exact schema returned bytools/list:
Mutation inputs
Guarded mutation tools expose applicable fields directly in theirinputSchema:
The fields are forwarded to the underlying Forge capability as safety headers
and request-body values. They are not generic prompt instructions.
Output limits
Tool text content is bounded to protect the MCP session. Successful results also include the underlying object instructuredContent.result. Search tools expose
their own cursor or offset semantics. forge_inventory_search additionally
returns resultCount, totalMatching, hasMore, nextOffset, and a
pagination object.
Do not treat a bounded search page as an organization-wide total.
forge_activity_aggregates_get computes exact totals across all activity that
matches its canonical filters, while returning bounded dimension breakdowns.
forge_llm_gateway_usage_get does the same for usage observed through Forge LLM
Gateway. Search tools should be continued using the pagination fields returned
by that specific tool.
MCP call audit records store the tool, capability, decision, reason, request ID,
and redacted bounded input/output summaries. Inputs containing credential-shaped
fields are redacted from the summary.