Search Strings
search_stringsSearch provider-defined string objects with literal or regex matching to find text in reverse-engineered artifacts. Results are deterministic over defined literals, not all bytes.
Instructions
Search every provider-defined string object using literal matching by default or regex when requested. Results are deterministic and complete over those defined objects, not every text sequence in artifact bytes. Ghidra may omit packed or undefined literals, including Rust strings; an empty result does not prove text is absent. If an address is known, read_bytes and xrefs inspect its bytes and references. Hopper retains typed byte decoding, native display, and explicit decoding unknowns. Adjacent long-literal fragments match independently. Hopper regex mode uses ECMAScript Unicode syntax in a cancellable worker; a matching deadline leaves its API usable.
Example tool call
This call uses example arguments supplied in the tool’s input schema.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"mode": "literal",
"pattern": "authorization failed",
"case_sensitive": false
},
"name": "search_strings"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| mode | No | Operation mode that selects the requested behavior. | |
| pattern | Yes | The literal text or regex pattern to search for | |
| document | No | The document name | |
| case_sensitive | No | Whether to match case |