beam_mcp: JSON boolean and null tool arguments reach dispatch as strings
ScriptKittyOS beam_mcp
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| ScriptKittyOS beam_mcp |
| No fix yet |
| ScriptKittyOS beam_mcp |
| No fix yet |
Original description
Incorrect Type Conversion or Cast vulnerability in BeamMCP.Server in ScriptKittyOS beam_mcp allows an MCP client's JSON true, false and null tool arguments to reach the host's dispatch function as the strings "true", "false" and "nil". After BeamMCP.Schema.validate/2 accepted a value as a boolean, normalize_arguments/2 passed every argument through to_json_value/1, whose atom clause converts true, false and nil to strings. A string is truthy in Elixir, so a host that tests a boolean argument, for example if args.dry_run, takes the opposite branch for false, and a guard such as confirm: false reads as set.