Skip to content
Squatch MCP

dev.workers.3labsio.policy-gate/policy-gate

dev.workers.3labsio.policy-gate/policy-gate

by dev.workers.3labsio.policy-gate· v0.2.0Source: Official MCP Registry

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: Low3 findings

Severity: LowStatus: OpenSQ-TOOL-META-INSUFFICIENT

Description too thin to determine behavior

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.

Severity: LowStatus: OpenSQ-TOOL-META-INSUFFICIENT

Description too thin to determine behavior

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.

Severity: LowStatus: OpenSQ-CONFORMANCE-MODERN-FAILURE

Protocol conformance checks failed

The server failed one or more MCP protocol conformance checks.

First seen · Last seen

Suggested fix: Review the failed checks against the MCP specification.

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