Skip to content
Squatch MCP
Sign in

Polyfork low-poly 3D assets

dev.polyfork/polyfork

by dev.polyfork· v1.0.0Source: Official MCP Registry
Sign in to watchSign in to claim this server

Findings

Detected by Squatch rules from the server's metadata and protocol behavior. Latest completed scan: .

Severity: High1 finding

Severity: HighStatus: 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

Suggested fix: Require MCP authorization for servers that expose state-changing tools.

Severity: Medium2 findings

Severity: MediumStatus: OpenSQ-TOOL-INJECTION-INSTRUCTIONS

Instructions addressed to the AI model

Model-facing text contains instructions addressed to the AI model rather than a description of the tool (for example to override prior instructions, to act before using tools, or to react to trigger phrases).

First seen · Last seen

Suggested fix: Describe what the tool does and its parameters. Do not include instructions to the model about other tools, the user or the conversation.

Severity: MediumStatus: OpenSQ-TOOL-CROSS-TOOL-REFERENCE

Gives instructions about other tools

Model-facing text gives the AI model instructions about tools that this server does not provide (tool shadowing).

First seen · Last seen

Suggested fix: Describe only this server's own tools.

Severity: Low1 finding

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: Info1 finding

Severity: InfoStatus: OpenSQ-TOOL-EXFIL-SHAPED-PARAM

Free-text parameter commonly used to collect conversation data

A free-text parameter has a name commonly abused to collect conversation, prompt or environment data.

First seen · Last seen

Suggested fix: Constrain the parameter (enum, maxLength) or rename it to reflect its purpose; never ask the model to fill it with conversation content.

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.

How Squatch scans servers