Skip to content
← All products

Local action layer for agent builders

Combine actions into governed workflows.

Turn isolated account tasks into inspectable loops: discover, enrich, plan, ask for approval, execute approved steps, and write outcomes to local history. Agents get tools; humans keep control.

Request handoff See what ships
Validated registry
196
local actions · 10 MCP tools
Read-only surface
131
safer discovery actions
Risk-gated surface
65
mutations require explicit approval
Action categories
12
jobs, feed, profile, network, messaging, more
mcp action registry 10 tools
196 registered actions read-only discovery plus gated execution
  • 131 read-only
  • 7 low
  • 12 medium
  • 18 high
  • 28 unsafe
confirm force redacted log
human-in-the-loop execution local session

What you can build by combining actions

The leverage is composition. A buyer can combine read-only discovery, profile/job/feed/message primitives, MCP calls, approval gates, and local run history into internal workflows instead of handing an agent uncontrolled browser access.

  • Recruiter loop with local memory

    Source candidates, enrich profile facts, draft an outreach plan, pause for human review, execute only approved items, and write outcomes to a local CRM file so candidates move through a visible pipeline.

  • Agent tool surface with brakes

    Let an agent list actions, inspect required inputs, run read-only steps, and stop when confirmation is required. The MCP layer gives a compact 10-tool interface instead of hundreds of exposed primitives.

  • Account operations review

    Use read-only actions across jobs, feed, profile, network, settings, notifications, and organization surfaces to create internal review queues before any externally visible action happens.

  • Workflow prototype faster than from scratch

    Start from a registry, CLI runner, MCP server, recruiter workflow, redacted logs, and local CRM shape instead of building every control surface yourself.

What ships in the handoff

Everything transfers as source you own: the working code, the demo data, the docs, and the limitations notes. One price, no subscription, no hosted dependency.

product
Professional-network workflow kit
price
$1,499
buyer
Agent builders, recruiters, sourcers, internal ops teams, and technical founders.

included

  • cliActions/ local action runner and registry
  • MCP stdio server with 10 registered tools
  • Recruiter workflow prototype and local CRM file shape

components

CLI action layer
Manual login, session status, action list/show/run, smoke checks, run history, license status, doctor output, and redacted local run logs.
Agent interface
A compact MCP server exposes listing, description, execution, run history, license status, and recruiter workflow tools instead of hundreds of one-off tools.

How intent becomes output

The operator path, start to finish. Each step is a real command surface, not a promise.

  1. 01

    Discover

    List the available local actions, inspect categories, and keep read-only discovery separate from mutating execution.

  2. 02

    Plan

    Use the recruiter prototype to source, enrich, plan outreach, and write a local CRM record before execution.

  3. 03

    Approve

    Low, medium, high, and unsafe actions require confirmation; unsafe actions also require force.

  4. 04

    Audit

    Review redacted run history locally; long MCP responses are trimmed while full redacted records remain on disk.

What's proven, what's excluded

The same diligence a technical buyer would run: what the code demonstrates locally, and what is deliberately left out of a clean handoff.

✓ proven

  • Registry validated

    The root check validates 196 action definitions with unique IDs, checked needs, and mode/risk/category splits.

  • Checks pass locally

    The inventory records npm run check passing on June 26, 2026 with syntax, registry, runner, network, feed, profile, resolve, stream, and redaction selftests.

  • Risk posture is explicit

    The code has confirm/force gates on every mutating action; marketing copy avoids promises about safety, compliance, production rate limits, or live freshness.

! excluded

  • Not a hosted service

    No hosted SaaS, cloud billing, packaged installer, Stripe integration, marketplace listing, customers, or revenue are included.

  • Live proof needs refresh

    Live behavior depends on account state, UI/API changes, permissions, locale, and rate limits.

  • Buyer controls use

    Commercial launch should add counsel-reviewed terms, warnings, data disclosures, behavior safeguards, and fresh live testing.

Build it yourself, or start from the source

Build from scratch Pullmesh handoff
Give an agent direct browser access and hope it behaves. Start with a compact MCP surface, explicit action registry, approval gates, and local redacted run logs.
Build the action registry, CLI runner, MCP server, and workflows in separate experiments. Receive the combined action layer as source and decide which surfaces to productize.
Discover risky actions only after a workflow mutates state. Inspect read-only, low, medium, high, and unsafe classifications before execution.

Request handoff

Give agents useful actions without giving up control.

Request the handoff to review the registry, MCP surface, support window, and commercial-use boundaries before transfer.

Request handoff