Signals Corps Get early access
Menu

Solutions · By initiative

Say yes to AI agents in every team. Keep the controls you need.

Signals Corps lets IT & Security teams say yes to agents in sales, marketing, finance, and engineering, with checks and approvals in place.

Get early access
Supply Chain

The problem

An agent acts with the access of the person who set it up.

Every team now connects agents to email, the CRM, shared drives, or a terminal, so one person's agent can cause a problem for the whole company.

Research from across the industry shows how far agents have spread, and into which data.

27%

of white-collar employees in the US use AI at work a few times a week or more.

Gallup's quarterly survey of US employees, 2025. The share has risen 12 points since 2024.

AI use at work now reaches well past the engineering team.

Gallup, June 2025

68%

of employees have already put sensitive company or customer data into an AI tool.

Survey of 1,500 full-time US employees at companies with 100 to 10,000 staff, excluding IT and security professionals.

Customer data reaches AI tools whether or not anyone approved it.

Merge, The 2026 State of Enterprise AI Governance, 2026

73%

of developers who use AI coding assistants or agents use them every day.

Stack Overflow 2026 Developer Survey, more than 30,000 respondents.

Coding agents are part of daily engineering work, alongside the agents every other team uses.

Stack Overflow, October 2026

Across your organization

One set of controls for every team's agents.

Each team's agents bring their own risk, from a blocklisted email domain to a GDPR breach.

Sales

Protect your email domain

A burst of agent email can get your domain blocklisted, and then nobody's email arrives. Runtime holds bulk sends for approval, and Supply Chain shows which devices have an outreach skill or email connector.

Marketing

Keep customer data where GDPR allows

Runtime blocks an agent copying customer records to a tool nobody has assessed, and Control Plane shows every device with a CRM connector.

Finance and operations

Know what reaches the shared drive

See which skills and connectors can read and write finance folders, and block the ones nobody has reviewed.

Engineering

Give developers coding agents

Runtime blocks reads of .env files and puts destructive commands in front of a person, while npm test runs as usual.

What changes

Teams keep their agents. IT & Security teams keep control.

Inventory

Know which agents each team uses

Control Plane lists each agent on each device, from the Claude desktop app on a sales laptop to Claude Code on an engineer's, with the skills, plugins, and connectors each one loads.

Decisions

Decide what each team can connect

Supply Chain checks each skill against open Supply Chain Agent Threat Rules (ATR). New components start unreviewed, and you mark each one trusted or blocked.

Approvals

Risky actions wait for a person

Set a rule to ask for approval, and the action, a bulk email send or a database change, waits until IT & Security teams approve it in Control Plane.

Privacy

The checks stay on the device

Runtime decides on the device with local rules. Prompts, email content, customer records, and file paths stay there, so checking an agent doesn't create a new copy of personal data.

How it works

Start by watching. Add enforcement where the risk justifies it.

A typical rollout takes about four weeks, and nothing is enforced until you turn it on.

  1. Week 0Try it on a few devices

    Push one package through your device management tool, such as Jamf, Iru, or Intune, to a few devices in different teams.

  2. Week 1 · Supply ChainSee what each team uses

    Review the agents, skills, and connectors on each device. Trust what teams rely on and block what matches a critical rule.

  3. Week 2 · RuntimeWatch actions in log mode

    See which emails, CRM reads, and commands your rules would have stopped, while nothing is stopped.

  4. Week 3 · RuntimeAsk for approval on the riskiest actions

    For example bulk email sends, exports of customer records, and terraform destroy.

  5. Week 4Block what should never happen, and expand

    Block customer data leaving for unapproved destinations, then roll out to every team that uses agents.

In Control Plane

One view of every team's agents.

Open any agent, skill, or connector to see who has it, whether anyone has reviewed it, and what it has tried to do.

  • Every agent and connector by device, with its trust status
  • Allowed, approval, or blocked, with the matched rule on each action
  • Approval requests waiting, with who can approve them

Example deployment

When a connector isn't allowed yet.

Illustrative example

A 450-person company in Germany keeps Claude away from Salesforce during a GDPR review.

This company is fictional. The numbers come from a modelled fleet, not a customer.

Read the example
  • A Salesforce connector found on 23 devices the Claude admin setting didn't cover
  • A Salesforce plugin blocked on all 6 devices that had it
  • 17 hand-added Salesforce MCP servers down to 0 by week 3

What it costs

Priced per device. Always predictable.

Supply Chain and Runtime are priced per device, alone or together, with free devices on every plan. Your bill depends on how many devices you cover, so heavier agent use doesn't change it, and finance can plan ahead.

Estimate your cost

Questions

What buyers ask us.

Which agents does it work with?

The agents your teams already use, including Claude Code and the Claude desktop app, Codex and ChatGPT, Cursor, Windsurf, and agents built on other frameworks.

Can we stop a sales agent damaging our email domain?

Yes. Set a Runtime rule on email sends, such as approval above a set number an hour, and Supply Chain shows every device with an outreach skill or email connector.

Can we keep agents away from our CRM until our GDPR review is done?

Yes. Find every device with a CRM connector in Control Plane, block the plugins and skills that bring one, and block agent access to the CRM with a Runtime rule until your review is signed off.

Will employees feel watched?

You can tell employees exactly what is collected. Control Plane receives which agents and components are installed and which rule each action matched. Prompts, email content, customer records, usernames, and file paths stay on the device.

Do we need both modules?

Start with the module that fits your first problem: Supply Chain to see what each team uses, or Runtime to check what agents do. Add the other when you're ready. One package on each device runs both.

Modules used

Built on these modules.

Before trust

Supply Chain

Find every AI agent on every device. Check every skill it loads.

See which AI agents run on each device and which identities they can reach, check the skills they load, and block what you don't trust.

Explore Supply Chain
While agents act

Runtime

Control risky agent actions. Before they execute.

Stop unsafe agent actions in real time while safe work carries on.

Explore Runtime

Early access

Reduce agent risk without slowing your teams down.

Start reducing agent risk before general release by checking agent components, controlling agent actions, and hunting through your AI security logs. Signals Corps Control Plane opens to early sign ups in the next few weeks, so join the waitlist with your company email.

Get early access