Recruit Crm
SuspiciousAudited by ClawScan on May 10, 2026.
Overview
This appears to be a legitimate Recruit CRM integration, but it should be reviewed because it enables broad authenticated API actions, including changing or deleting recruiting data, without documented scope or approval controls.
Install this only if you trust Membrane and need agent access to Recruit CRM. Use a least-privileged Recruit CRM connection, prefer predefined actions, and require explicit confirmation before any operation that creates, updates, deletes, uploads, or bulk-changes records.
Findings (4)
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.
An agent using this skill could make broad changes to Recruit CRM records, including deleting or modifying candidates, jobs, users, notes, or files if directed incorrectly.
This documents a raw authenticated API escape hatch with mutating and deleting methods. For HR/recruiting data, that is high-impact and the artifact does not define approval, scope, or rollback controls.
When the available actions don't cover your use case, you can send requests directly to the Recruit CRM API through Membrane's proxy... Common options: ... HTTP method (GET, POST, PUT, PATCH, DELETE).
Prefer scoped Membrane actions, require explicit user confirmation before any create/update/delete operation, restrict raw proxy use to reviewed endpoints, and use audit logs or backups for reversible changes.
The skill can act through the connected Recruit CRM account and will inherit whatever permissions that account or connection has.
The skill requires delegated Membrane and Recruit CRM account access. This is expected for the integration, but it gives the agent access through an authenticated connection.
Membrane handles authentication and credentials refresh automatically... membrane login --tenant... membrane connect --connectorId=CONNECTOR_ID --json
Connect using the least-privileged Recruit CRM account practical for the task, review Membrane connection permissions, and revoke the connection when it is no longer needed.
Installing or running npm packages gives third-party CLI code access to the local environment where it is executed.
The setup uses a globally installed npm CLI and an unpinned `@latest` npx command. This is central to the stated purpose, but users should trust the package source and version.
npm install -g @membranehq/cli ... Use `npx @membranehq/cli@latest action list ...`
Install the CLI only from the official npm package, consider pinning a known version, and run it in an environment appropriate for handling Recruit CRM data.
Candidate, company, job, note, or file data may pass through Membrane while the integration operates.
Recruit CRM requests and possibly sensitive recruiting data are routed through Membrane's proxy. The proxy use is disclosed and purpose-aligned, but users should understand the data path.
send requests directly to the Recruit CRM API through Membrane's proxy... Membrane automatically... injects the correct authentication headers
Review Membrane's security and privacy terms, avoid sending unnecessary sensitive data, and ensure the connected Recruit CRM account has appropriate permissions.