Severity: MediumStatus: OpenSQ-SERVER-AUTH-NONE-WRITE
State-changing tools available without authentication
The remote server lists state-changing tools without requiring authentication.
First seen · Last seen
Sandboxd Code Run
com.saastemly/sandboxd-code-run
Findings
Detected by Squatch rules from the server's metadata and protocol behavior. Latest completed scan: .
Severity: Medium3 findings
Suggested fix: Require MCP authorization for servers that expose state-changing tools.
Severity: MediumStatus: OpenSQ-TOOL-OVERLY-BROAD
Runs arbitrary code with open-world access
The tool runs code, commands or queries supplied at call time and does not declare a closed-world scope.
First seen · Last seen
Suggested fix: Narrow the tool to specific operations, or declare and enforce a closed-world sandbox.
Severity: MediumStatus: OpenSQ-TOOL-OVERLY-BROAD
Runs arbitrary code with open-world access
The tool runs code, commands or queries supplied at call time and does not declare a closed-world scope.
First seen · Last seen
Suggested fix: Narrow the tool to specific operations, or declare and enforce a closed-world sandbox.
Severity: Low3 findings
Severity: LowStatus: OpenSQ-REPO-MISSING
No source repository linked
No source repository is linked in the registry entry.
First seen · Last seen
Suggested fix: Add a repository to server.json.
Severity: LowStatus: OpenSQ-TOOL-DESTRUCTIVE-NO-ANNOTATION
Destructive tool without annotations
A tool that appears to delete data, change permissions or run code declares no tool annotations.
First seen · Last seen
Suggested fix: Declare readOnlyHint, destructiveHint, idempotentHint and openWorldHint so clients can request confirmation.
Severity: LowStatus: OpenSQ-TOOL-DESTRUCTIVE-NO-ANNOTATION
Destructive tool without annotations
A tool that appears to delete data, change permissions or run code declares no tool annotations.
First seen · Last seen
Suggested fix: Declare readOnlyHint, destructiveHint, idempotentHint and openWorldHint so clients can request confirmation.
What this scan does not cover
- Squatch never calls a server's tools, so it cannot see what they actually do at run time.
- It scans without credentials: tools behind authentication may not be visible.
- It does not review source code, dependencies or the publisher's infrastructure.
- A server can change behavior between scans; monitoring compares each scan with the last.
- Classifications come from tool names, descriptions and schemas, which the publisher controls.