Struct CodeModeToolBuilder 

pub struct CodeModeToolBuilder { /* private fields */ }

Builder for standard Code Mode tool definitions.

Implementations

impl CodeModeToolBuilder

pub fn new(code_format: &str) -> Self

Create a new tool builder for the given code format.

pub fn build_tools(&self) -> Vec<ToolInfo>

Build the standard Code Mode tools.

pub fn build_validate_tool(&self) -> ToolInfo

pub fn build_execute_tool(&self) -> ToolInfo

Build the execute_code tool definition.

Deliberately carries NO annotations. readOnlyHint/destructiveHint are the hints a host reads to decide whether a call needs human confirmation, and this tool runs caller-supplied code against the app’s op surface — a hardcoded “read-only, non-destructive, idempotent” would be a false safety claim for any app that exposes a single mutating op, and nothing here enforces that it does not.

The durable fix is to DERIVE the hints rather than hardcode them, and the pieces already converge: OperationRegistry::lookup_category (config.rs), the ValidationPipeline the generated handler already owns at its metadata() call site (pmcp-code-mode-derive), and the per-script fold precedent in javascript.rs (is_read_only); the full Cedar/AVP design layers on policy_annotations.rs. Until then the MCP defaults (readOnlyHint = false, destructiveHint = true) are the honest answer.