Render

ReviewAudited by ClawScan on May 10, 2026.

Overview

The skill is a coherent Render integration, but it gives the agent broad authenticated power to call the Render API, including mutating or deleting resources, without clear approval or scope limits in the provided instructions.

Before installing, understand that this skill can help manage Render through an authenticated Membrane connection and may make direct Render API calls. Use a least-privilege account, review any proposed write or delete operation carefully, and avoid letting the agent use the raw proxy for destructive actions without explicit confirmation.

Findings (3)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

A broadly interpreted user request could lead the agent to change or delete Render services, deployments, databases, or related project resources.

Why it was flagged

This gives the agent a raw authenticated API escape hatch, including destructive methods, without visible scoping, dry-run, rollback, or explicit confirmation requirements in the provided instructions.

Skill content
When the available actions don't cover your use case, you can send requests directly to the Render API through Membrane's proxy... Common options: ... HTTP method (GET, POST, PUT, PATCH, DELETE).
Recommendation

Use this only with explicit instructions for each intended change; require confirmation before POST, PUT, PATCH, or DELETE requests, and prefer read-only discovery or pre-built actions where possible.

What this means

The agent may be able to act through the authenticated Render connection with the permissions granted during login.

Why it was flagged

The skill uses delegated Membrane/Render authentication and automatic credential refresh, which is expected for the integration but grants ongoing account access.

Skill content
Membrane handles authentication and credentials refresh automatically... membrane login --tenant --clientName=<agentType> ... membrane connection ensure "https://render.com/" --json
Recommendation

Connect with the least-privileged Render account or token available, and revoke the Membrane connection when it is no longer needed.

What this means

The behavior may depend on whatever CLI version is current at install time.

Why it was flagged

The setup relies on installing/running the latest npm release of the Membrane CLI. This is central to the skill, but @latest means the reviewed artifact does not pin the exact CLI version.

Skill content
npm install -g @membranehq/cli@latest ... Use `npx @membranehq/cli@latest action list ...`
Recommendation

Install the CLI from the official package source and consider pinning a known version in controlled environments.