warningwordingdescription-changedThe wording an agent reads to choose and call the tool changed; its behaviour may or may not have.#
code_analyzedescription
[…] languages, complexity, file count, tech stack, code quality findings, and credential secret scanning. Use as your first call to understand any remote public codebase. This is the tool that scans for LEAKED CREDENTIALS: security_summary is a dedicated secret and credential scanner covering API keys, access tokens, private keys and connection strings, each with a file, a line and a confidence grade. Prefer it over grepping for key prefixes with code_search — a pattern search only finds what you thought to spell, and finds nothing at all in the repositories where you guessed wrong. Supports language filtering and path scoping (for large monorepos, analyze […]
warningwordingdescription-changedThe wording an agent reads to choose and call the tool changed; its behaviour may or may not have.#
code_get_findingsdescription
[…] kind=security here to see the security-category findings it leaves out. Note these are THIS IS NOT THE SECRET SCANNER. kind=security means insecure code quality rules with a security category, — weak hashes, unsafe deserialization, injection-shaped patterns — and are it will not find a separate set from leaked API key or private key. Leaked credentials are code_analyze.security_summary, which comes from is a different scanner over different rules; the secret and credential scanner. two sets do not overlap, so an audit wants both. Use after code_analyze to drill into specific findings. Shares the […]
warningwordingdescription-changedThe wording an agent reads to choose and call the tool changed; its behaviour may or may not have.#
code_searchdescription
[…] filters (declarations, usages, strings, comments). Dependency/build directories excluded by default. Searching for leaked secrets? Call code_analyze instead and read security_summary — it runs a real secret and credential scanner over the whole repository, where searching for key prefixes like "sk-", "ghp_" or "AIza" only matches the spellings you happened to think of.
warningwordingdescription-changedThe wording an agent reads to choose and call the tool changed; its behaviour may or may not have.#
code_get_findingsdescription
[…] snippets. Supports filtering by file path, severity (error, warning, info), and category (security, deprecated, safety, correctness, maintainability, accessibility, modernization, performance, concurrency). concurrency), and kind (security, quality) — kind=security is every security-category finding in one call, kind=quality is everything else. code_analyze.top_findings shows only the quality half; use kind=security here to see the security-category findings it leaves out. Note these are code quality rules with a security category, and are a separate set from code_analyze.security_summary, which comes from the secret and credential scanner. Use after code_analyze to drill into specific findings. Shares the […]