[GH-ISSUE #2213] [Bug] Frida input errors say "correct the listed arguments" but list none #738

New issue

Closed

opened 2026-10-15 18:27:50 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-15 18:27:50 +00:00

Owner

Originally created by @kaoru0822-kitauji on GitHub (Oct 12, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/2213

Observed behavior

Most Frida input rejections return an invalid_request with no issues. The remediation says "Correct the listed arguments and retry", but nothing is listed:

# MCP, with a session ID that is not open
frida_session_status / close_frida_session / load_frida_script / resume_frida_session
→ {"error":{"code":"invalid_request","message":"Analysis input is invalid. Check the arguments and try again.","remediation":{"action":"Correct the listed arguments and retry."}}}

# CLI
$ rea instrument-with-frida attach abc --script 'send(1)'            # PID is not a positive integer
$ rea instrument-with-frida attach 123                                 # neither --script nor --script-file
$ rea instrument-with-frida attach 123 --script x --script-file a.js   # both
→ the same bare invalid_request, with no indication of which argument is wrong

The same happens for an unknown script_id in unload_frida_script, and for a load_frida_script file source that cannot be read (only EACCES/EPERM gets a typed error).

Reproduction

Current main 7ae3c50a9. Call any of the MCP tools above with session_id: "00000000-0000-4000-8000-000000000009", or run the CLI commands above.

Expected behavior

Each rejection names the argument and the reason, as other REA input errors do. For example, session_id: "No open Frida session …"; target: "attach mode needs a positive integer process ID"; script: "provide exactly one of --script or --script-file"; path: "cannot read Frida script file … ".

Cause

FridaInstrumentationManager (load_frida_script, resume_frida_session, unload_frida_script, close_frida_session), registerFridaTools (frida_session_status) and src/cli/fridaCommands.ts construct new AnalysisInputError(operation) without any AnalysisInputIssue.

Originally created by @kaoru0822-kitauji on GitHub (Oct 12, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/2213 ### Observed behavior Most Frida input rejections return an `invalid_request` with no `issues`. The remediation says "Correct the listed arguments and retry", but nothing is listed: ```text # MCP, with a session ID that is not open frida_session_status / close_frida_session / load_frida_script / resume_frida_session → {"error":{"code":"invalid_request","message":"Analysis input is invalid. Check the arguments and try again.","remediation":{"action":"Correct the listed arguments and retry."}}} # CLI $ rea instrument-with-frida attach abc --script 'send(1)' # PID is not a positive integer $ rea instrument-with-frida attach 123 # neither --script nor --script-file $ rea instrument-with-frida attach 123 --script x --script-file a.js # both → the same bare invalid_request, with no indication of which argument is wrong ``` The same happens for an unknown `script_id` in `unload_frida_script`, and for a `load_frida_script` file source that cannot be read (only EACCES/EPERM gets a typed error). ### Reproduction Current main 7ae3c50a9. Call any of the MCP tools above with `session_id: "00000000-0000-4000-8000-000000000009"`, or run the CLI commands above. ### Expected behavior Each rejection names the argument and the reason, as other REA input errors do. For example, `session_id`: "No open Frida session …"; `target`: "attach mode needs a positive integer process ID"; `script`: "provide exactly one of --script or --script-file"; `path`: "cannot read Frida script file … ". ### Cause `FridaInstrumentationManager` (`load_frida_script`, `resume_frida_session`, `unload_frida_script`, `close_frida_session`), `registerFridaTools` (`frida_session_status`) and `src/cli/fridaCommands.ts` construct `new AnalysisInputError(operation)` without any `AnalysisInputIssue`.

bsakaguchi

2026-10-15 18:27:50 +00:00