SkillTotal

Is fastmcp-slim safe?

Some risk - review before installing
Notable — review in context (capabilities are not malware):
  • Python shell/command execution
  • Unsafe deserialization
  • Python filesystem read

What to do: Read the findings below before installing: each one opens the exact line of code it was found on.

fastmcp-slim is a PyPI package analyzed by SkillTotal's deterministic static scanner. The scan found no malicious indicators, though 2 risky constructs are reported for review. It can: delegated authentication, filesystem read, filesystem write, mcp tools detected and shell execution — capabilities are what the code can do, not a verdict on intent. Risk score 30/100 (medium).

fastmcp-slim 4.0.11

python_package · pypi:fastmcp-slim
MEDIUM
30
/ 100 risk score
Snapshot · scanned Oct 8, 2026 · fastmcp-slim@4.0.11 · engine 0.56.4 / ruleset 62

Automated static-analysis result. It can contain false positives and false negatives, and is not a claim about the intent of fastmcp-slim's authors. Report a false positive.

Capabilities — what this component can do (not a risk score):
delegated authenticationfilesystem readfilesystem writemcp tools detectedshell execution

Behavioral traits

How this component maps to the CSA agentic threat model. Descriptive — it never affects the risk score.

Tool surface
Tool Usage
Execution authority
Tool Access Control / Direct Tool Access
Filesystem reach
Tool Execution Context
Network exposure
Interaction & Communication
Delegated authentication
Tool Execution Context / User Delegated Credentials
Unsafe deserialization
General Protections / Input Validation

Findings (7)

HIGHUnsafe deserializationST-DESERIALIZE-PY

It loads data with a format that can rebuild arbitrary objects (e.g. pickle, or unsafe YAML).

parsed = yaml.load(frontmatter_text, Loader=yaml.BaseLoader)  # noqa: S506

Why it matters: Feeding such a loader untrusted data can execute code hidden inside that data.

Fix: Deserialize untrusted data with a safe format/loader: JSON, or yaml.safe_load / Loader=SafeLoader. Reserve pickle/marshal for data you fully control.

HIGHPython shell/command executionST-SHELL-PY

The component can run operating-system commands or spawn processes.

process = await asyncio.create_subprocess_exec(
        *cmd,
        env=env,
        start_new_session=sys.platform != "win32",
    )
subprocess.run([cmd, "--version"], check=True, capture_output=True)
process = subprocess.run(
            [npx_cmd, inspector_cmd, *uv_cmd],
            check=True,
            env=env,
        )
process = subprocess.run(cmd, check=True, env=env)
process = subprocess.run(cmd, check=True, env=env)
subprocess.run(
            [
                "powershell.exe",
                "-NoLogo",
                "-NoProfile",
                "-NonInteractive",
                "-Command",
                _WINDOWS_ACL_SCRIPT,
            ], …
result = subprocess.run(
                [claude_in_path, "--version"],
                check=True,
                capture_output=True,
                text=True,
            )
result = subprocess.run(
                    [str(path), "--version"],
                    check=True,
                    capture_output=True,
                    text=True,
                )
subprocess.run(
                [gemini_in_path, "--version"],
                check=True,
                capture_output=True,
            )
subprocess.run(
                    [str(path), "--version"],
                    check=True,
                    capture_output=True,
                )
return subprocess.run(
            windows_batch_command_line(command),
            executable=_windows_command_processor(),
            check=True,
            capture_output=True,
            text=True,
        )
return subprocess.run(command, check=True, capture_output=True, text=True)
subprocess.run(["open", url], check=True, capture_output=True)
subprocess.run(["xdg-open", url], check=True, capture_output=True)
process = subprocess.run(cmd, check=True)
process = await asyncio.create_subprocess_exec(
                *cmd,
                stdin=None,
                stdout=None,
                stderr=None,
                # Own process group so _terminate_process can kill the whole tree …
subprocess.run(
                [
                    "uv",
                    "init",
                    "--project",
                    str(output_dir),
                    "--name",
                    "fastmcp-env",
                ] …
subprocess.run(
                    [
                        "uv",
                        "python",
                        "pin",
                        self.python,
                        "--project",
                        str(outpu …
subprocess.run(
                [
                    "uv",
                    "add",
                    *dependencies,
                    "--no-sync",
                    "--project",
                    str(output_dir), …
subprocess.run(
                    [
                        "uv",
                        "add",
                        "-r",
                        str(req_path),
                        "--no-sync",
                        "--project" …
subprocess.run(
                    [
                        "uv",
                        "add",
                        "--editable",
                        *editable_paths,
                        "--no-sync",
                        " …
subprocess.run(
                ["uv", "sync", "--project", str(output_dir)],
                check=True,
                capture_output=True,
                text=True,
            )

Why it matters: Powerful and often legitimate — confirm the commands aren't built from untrusted input.

Fix: Confirm the command and its arguments are fully controlled and not derived from untrusted input; avoid shell=True.

MEDIUMServer bound to all network interfacesST-EXPOSE-BIND

A server is bound to all network interfaces (0.0.0.0), not just your own machine.

local_host = {"0.0.0.0": "127.0.0.1", "::": "::1"}.get(host, host)  # noqa: S104
_WILDCARD_HOSTS = frozenset({"0.0.0.0", "::"})  # noqa: S104
examples=["127.0.0.1", "0.0.0.0", "localhost"],  # noqa: S104 - schema example values, not a bind default

Why it matters: Without authentication, other hosts on the network can reach it.

Fix: Bind to 127.0.0.1 for local-only use, or require authentication and restrict access if remote exposure is intended.

MEDIUMPython filesystem readST-FS-PY-READ

The component reads files from disk.

app_bridge_js = app_bridge_cache.read_text(encoding="utf-8")
with open(Path(server_spec), encoding="utf-8") as f:
data = json.loads(path.read_text(encoding="utf-8"))
return model.model_validate_json(path.read_text(encoding="utf-8"))
text = path.read_text(encoding="utf-8")
text = path.read_text(encoding="utf-8")
text = path.read_text(encoding="utf-8")
content = config_file.read_text(encoding="utf-8").strip()
with open(config_path, encoding="utf-8") as f:
with open(config_path, encoding="utf-8") as f:
content := file_path.read_text(encoding="utf-8").strip()
content: str | bytes = await self._async_path.read_bytes()
content = await self._async_path.read_text(encoding=self.encoding)
return main_file_path.read_text(encoding="utf-8")
return full_path.read_text(encoding="utf-8")
return full_path.read_text(encoding="utf-8")
content = main_file.read_text(encoding="utf-8")
with open(config_path, encoding="utf-8") as f:
with open(self.path, "rb") as f:
with open(self.path, "rb") as f:
with open(self.path, "rb") as f:
data = json.loads(cache_path.read_text())

Why it matters: Usually legitimate, but worth confirming it can't be steered into reading sensitive files.

Fix: Confirm which files are read and that paths cannot be influenced by untrusted input to reach sensitive locations.

MEDIUMPython filesystem write/deleteST-FS-PY-WRITE

The component writes or deletes files on disk.

app_bridge_cache.write_text(app_bridge_js, encoding="utf-8")
with open(output_path, "w") as f:
output_path.write_text(script)
skill_path.write_text(skill_content)
config_file.write_text('{"mcpServers": {}}')
file_path.write_text(self.model_dump_json(indent=2), encoding="utf-8")
file_path.write_text(content.text, encoding="utf-8")
file_path.write_bytes(base64.b64decode(content.blob))
cache_path.write_text(
            json.dumps({"latest_version": latest_version, "timestamp": time.time()})
        )

Why it matters: Usually legitimate, but worth confirming the paths can't be controlled by untrusted input.

Fix: Confirm which files are written/deleted and that paths cannot be influenced by untrusted input.

LOWDelegated authentication (OAuth 2.0 / OIDC)ST-AUTH-DELEGATED

An OAuth 2.0 / OpenID Connect delegated-authentication flow was detected (authorization-code / refresh-token / token-exchange grant, an OIDC authorize/discovery endpoint or id_token, or a delegation library). Tools authenticate with the end user's delegated, scoped credentials rather than a long-lived embedded service credential. (25 occurrence(s) shown as evidence).

# These providers pull in heavy deps (authlib, cryptography, key_value.aio,
upstream_authorization_endpoint="https://login.example.com/oauth/authorize",
f"/.well-known/openid-configuration{issuer_path}",
# Always register /.well-known/openid-configuration regardless of path depth.
#    /{prefix}/.well-known/openid-configuration arrives here as
#    /.well-known/openid-configuration.
"/.well-known/openid-configuration",
"(`{issuer}/.well-known/openid-configuration`) unless overridden in "
Fetches ``{issuer}/.well-known/openid-configuration`` and returns its
config_url = issuer.rstrip("/") + "/.well-known/openid-configuration"
from authlib.common.security import generate_token
access_token, and for OIDC providers may include id_token,
to verify a different token (e.g., the OIDC id_token for providers
# When alternate verification is in use (e.g., id_token
# JWTs for both access_token and id_token, which would cause
Replaces `authlib.integrations.httpx_client.AsyncOAuth2Client` for the OAuth
proxy's upstream token-endpoint calls. authlib's httpx integration imports the
legacy `httpx` package — which authlib does not declare as a dependency and
- form-encoded POST token requests with authlib's default headers
- `client_secret_basic` (latin-1 basic auth, authlib-style), `client_secret_post`,
- `OAuthError` (authlib's httpx-free core error class) raised for RFC 6749
from authlib.integrations.base_client import OAuthError
Drop-in replacement for the slice of authlib's `AsyncOAuth2Client` that
# Mirror authlib's OAuth2Token: derive expires_at from expires_in so

Fix: Delegated auth is a lower-blast-radius execution context than an embedded static credential. Confirm the requested scopes are minimal and that tokens are never logged or forwarded off-host.

LOWMCP tool surface detectedST-MCP-DETECTED

An MCP tool surface (manifest or tool definitions) was found.

server = FastMCP("Platform")
"""Shared dispatch logic for @app.tool() and @app.ui() calling patterns."""
(``@app.tool``), and the Prefab renderer resource.  Backend tools
# @app.tool() — backend tools called by the UI
@app.tool("custom_name")
server = FastMCP(self.name)
mcp = FastMCP("My Server")
mcp = FastMCP("My Server")
mcp = FastMCP("My Server")
mcp = FastMCP("My Server")
@mcp.tool(app=PrefabAppConfig())  # same as app=True
@mcp.tool(app=PrefabAppConfig(
mcp = FastMCP("My Server")
mcp = FastMCP("My Server")
mcp = FastMCP("My Server")
mcp = FastMCP("My Server")
mcp = FastMCP("My Server")
mcp = FastMCP("My Server")

Why it matters: Just context — review which tools it offers and their permissions.

Fix: Review the declared MCP tools and their permissions.

How attackers abuse these capabilities

Interactive labs on the attack class behind the rules above. They show the technique, not anything found in fastmcp-slim.

Check your own component

Run the same evidence-backed scan on any MCP server, agent skill, or package.

Scan your own component

How we determine this: deterministic static analysis (regex + AST), evidence-anchored, no code execution. Methodology →