Tools
A tool is a callable operation that an agent can invoke: an API endpoint, a script, a browser action, or an MCP server function. Tools are what connect agents to the outside world. Every tool call is wrapped in an AOCL envelope, budget-gated, and recorded in the VOLT evidence chain.
Four install paths
Paste an OpenAPI 3.x spec URL or upload the JSON. QuoxCORE parses the spec, extracts the endpoints as callable operations, and wraps each one in an AOCL-gated tool invocation. Suitable for most REST APIs.
Connect a Model Context Protocol server. QuoxCORE discovers the available tools via the MCP protocol and registers them automatically. QuoxMCP ships with 168 pre-wired tools. Third-party MCP servers can be added by URL.
Point at a Git repository containing a tool manifest. QuoxCORE clones the repo into a sandboxed execution environment and registers the tools declared in the manifest. Suitable for internal tooling and CLI wrappers.
Write a Python script in the built-in code editor. The script runs in a Docker sandbox with network and filesystem constraints set at install time. Each script invocation is budget-gated and produces an AOCL evidence event. The Toolsmith path is the developer-tier install path for custom automation.
The agent-tool matrix
The Assignments tab in the Tools view shows which agents can call which tools. The matrix is a grid: rows are tools, columns are agents, cells show the permission state (allowed, blocked, or not assigned).
Assignments can be changed individually (single cell toggle) or in bulk (select a tool row and apply to all agents). Bulk assignments emit an AOCL event recording which user changed which assignments and when.
The matrix is the enforcement surface. If an agent is not assigned a tool, it cannot call it — even if the tool is installed and available to other agents. This is how the platform implements least-privilege tool access.
Install-time budget
When a tool is installed, you can set a budget constraint: a maximum cost per invocation, a maximum number of calls per day, or both. Budget constraints are enforced at the AOCL layer before the tool is called. If a call would breach the constraint, it is blocked and logged as a DENY event.
Install-time budgets are one of the four budget scopes in QuoxCORE 2. The others are objective-level, execution-level, and iteration-level budgets set in the workflow builder.
Plugin durability
Tool configurations — including install parameters, assigned agents, and budget constraints — are stored server-side in the collector's SQLite database. They survive browser clears, re-deployments, and server restarts. A fresh browser with empty cache sees the same tool configuration as one that has been open for weeks.
This is the plugin durability guarantee introduced as part of the Stream PD work. Tool state is never held only in localStorage or IndexedDB. The server is always the source of truth.