We read every description in its 3 tools, from the live server, and the listing for 1.0.0. 6 checks, no findings.
Hidden instructionsNothing tells the agent to override its rules or keep things from you.
Passed
Invisible textNo invisible or direction-flipping characters.
Passed
Access to credentialsNo reaching for SSH keys, cloud credentials, wallets or the keychain.
Passed
Downloads and runs codeNo piping downloads into a shell or running encoded payloads.
Passed
Sends data outNo uploads of credential files or catch-all collection endpoints.
Passed
Leaked secretsNo API keys, tokens or private keys published by mistake.
Passed
Tool changes
None since Oct 26
Pinned tool set3
1 can change data · none can delete. Each tool is fingerprinted; every rescan compares against these hashes. Dashed access is read from the name.
Tool
Access
Description
Pinned hash
query_docs_filesystem_mintlify
read
Query documentation filesystem · Run a read-only shell-like query against a virtualized, in-memory filesystem rooted at `/` that contains ONLY the Mintlify documentation pages and OpenAPI specs. This is NOT a shell on any real machine — nothing runs on the user's computer, the server host, or any network. The filesystem is a sandbox backed by documentation chunks.
sha256:e9f0…d426
search_mintlify
read
Search documentation · Search across the Mintlify knowledge base to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about Mintlify, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages. If you need the full content of a specific page, use the query_docs_filesystem tool to `head` or `cat` the page path (append `.mdx` to the path returned from search — e.g. a result at `/some/page` is read with `head -200 /some/page.mdx`).
sha256:ab48…de07
submit_feedback
write
Submit documentation feedback · Report a problem with this documentation site so the docs team can fix it. Use when a documentation page is incorrect, outdated, confusing, incomplete, or has a broken example. This is for feedback about the documentation content itself — not for product support requests or feedback about this tool or assistant.
sha256:fcf9…eac9
Set pinned as sha256:db1a…9238 · still listed 7 h ago
