probe_stem_workflow

Read-only probe for Live 12.4 selected-time stem workflow support.

SERVERLivepilot SOURCElivepilot

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dreamrec-livepilot/probe-stem-workflow.md

WHAT IT DOES

What probe_stem_workflow does on Livepilot

AI agents call probe_stem_workflow to retrieve information from Livepilot without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why probe_stem_workflow is rated Low

This tool retrieves or queries information about stem workflow capabilities in Ableton Live 12.4 without creating, modifying, deleting, executing, or committing any side effects. The "read-only" qualifier confirms it performs no destructive or write operations. Blast radius is minimal—misuse would only expose workflow metadata.

From the tool's definition Tool description explicitly states "Read-only probe" and "selected-time stem workflow support" — it queries the state of Live 12.4 without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs probe_stem_workflow safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Livepilot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For probe_stem_workflow, this is the rule to start with:

probe_stem_workflow Allowed

probe_stem_workflow is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "probe_stem_workflow": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Livepilot, apply this rule, and every probe_stem_workflow call is checked against it from then on.

FAQ

Questions about probe_stem_workflow

What does the probe_stem_workflow tool do? +

Read-only probe for Live 12.4 selected-time stem workflow support. It is categorised as a Read tool in the Livepilot MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on probe_stem_workflow? +

Register the Livepilot MCP server in PolicyLayer and add a rule for probe_stem_workflow: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Livepilot. Nothing to install.

What risk level is probe_stem_workflow? +

probe_stem_workflow is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit probe_stem_workflow? +

Yes. Add a rate_limit block to the probe_stem_workflow rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block probe_stem_workflow completely? +

Set action: deny in the PolicyLayer policy for probe_stem_workflow. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides probe_stem_workflow? +

probe_stem_workflow is provided by the Livepilot MCP server (livepilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Livepilot, and thousands of servers like it.

This server

All 474 Livepilot tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →