State-changing tools available without authentication
The remote server lists state-changing tools without requiring authentication.
First seen · Last seen
Detected by Squatch rules from the server's metadata and protocol behavior. Latest completed scan: .
The remote server lists state-changing tools without requiring authentication.
First seen · Last seen
Suggested fix: Require MCP authorization for servers that expose state-changing tools.
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.
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.
Model-facing text references credential, key or configuration file locations unrelated to the tool's stated purpose.
First seen · Last seen
Suggested fix: Remove references to credential files, key stores and client configuration files.
A tool parameter asks the AI model to supply a password, token, key or similar credential, which the model can see and repeat.
First seen · Last seen
Suggested fix: Obtain credentials through server-side configuration or MCP authorization instead of tool arguments.
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.
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.
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.
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.
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.
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.
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.
Model-facing text contains shell command patterns such as piping downloads into a shell or recursive deletion.
First seen · Last seen
Suggested fix: Remove shell commands from descriptions.
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.
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.
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.
The tool's name and description do not state what it does.
First seen · Last seen
Suggested fix: Describe the action the tool performs, its target and its side effects.
No source repository is linked in the registry entry.
First seen · Last seen
Suggested fix: Add a repository to server.json.
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.
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.
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.
The tool's name and description do not state what it does.
First seen · Last seen
Suggested fix: Describe the action the tool performs, its target and its side effects.
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.
The tool's name and description do not state what it does.
First seen · Last seen
Suggested fix: Describe the action the tool performs, its target and its side effects.
The tool's name and description do not state what it does.
First seen · Last seen
Suggested fix: Describe the action the tool performs, its target and its side effects.
The tool's name and description do not state what it does.
First seen · Last seen
Suggested fix: Describe the action the tool performs, its target and its side effects.