Plugin Initialization
Tool Visibility Modes
Control which tools appear inlist_tools vs. CodeCall.
codecall_only (Recommended)
Default mode. Hides all tools from list_tools, exposes via CodeCall.
Best for: Large toolsets (20+), OpenAPI adapters, clean client experience.
codecall_opt_in
Tools must explicitly opt into CodeCall. All tools visible in list_tools by default.
Best for: Gradual migration, mixed direct/CodeCall access.
metadata_driven
Full control via per-tool metadata. No global assumptions.
Best for: Small toolsets, fine-grained control.
Per-Tool Metadata
Control individual tool behavior with thecodecall metadata field:
Metadata by Mode
Common Patterns
Hide from list_tools, available in CodeCall
Hide from list_tools, available in CodeCall
codecall_only mode.Visible everywhere
Visible everywhere
Direct access only, no CodeCall
Direct access only, no CodeCall
CodeCall meta-tools only
CodeCall meta-tools only
codecall:search, codecall:describe, etc.Global Tool Filtering
Filter tools globally withincludeTools:
ToolEntry with:
VM Configuration
Configure the JavaScript sandbox:VM Presets
Preset Details
- locked_down
- secure
- balanced
- experimental
Worker Pool Configuration (Advanced)
For OS-level memory isolation, configure the Worker Pool adapter:Worker Pool Presets by Security Level
Reference Sidecar Configuration (Pass-by-Reference)
The Reference Sidecar handles large data transfer between scripts and tools. Instead of passing full data through the VM, large values are stored externally with reference IDs.Sidecar Presets by Security Level
How Pass-by-Reference Works
Benefits:- Scripts don’t need to handle large data in memory
- VM stays lightweight and secure
- Tool results can exceed VM memory limits
- Reference IDs are opaque strings (no data leakage)
Embedding Configuration
Configure how tools are indexed for search:Strategy Comparison
TF-IDF Configuration
- Tool name (tokenized:
users:list→users,list) - Description (weighted 3x)
- Key terms from description (4+ characters, no stop words)
Embedding Configuration
Embedding strategy uses VectoriaDB internally. The model (~22MB) is downloaded on first use and cached locally.
Tool Search Tuning
Fine-tune howcodecall:search finds and ranks tools:
Scoring Mechanics
When a user searches for “list users”, the scoring works:Optimizing for Large Toolsets (100+)
For large toolsets, consider these optimizations:Direct Invocation
Configure thecodecall:invoke meta-tool for direct tool calls without VM overhead:
When to Use Direct Invoke
Performance Comparison
Error Response Format
Security Considerations
- allowedTools: Always specify an explicit allowlist in production
- No script execution: Direct calls cannot run arbitrary code
- Same tool access rules: Tool Access Control (whitelist/blacklist) still applies
- Audit logging: Direct calls are logged the same as scripted calls
Complete Configuration Example
Environment Variables
Override configuration via environment variables:Migration Guide
From Direct Tools to CodeCall
1
Add CodeCallPlugin
2
Mark Tools for CodeCall
3
Test Both Access Methods
Verify tools work via both direct calls and CodeCall.
4
Switch to codecall_only
5
Remove Direct Visibility
Related
Security Model
Security implications of configuration choices
Production Scaling
Performance tuning and monitoring