This record as markdown: /tools/io-github-dreamrec-livepilot/set-count-in-duration.md
What set_count_in_duration does on Livepilot
AI agents use set_count_in_duration to create or update resources in Livepilot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Livepilot environment.
Why set_count_in_duration is rated Medium
This tool modifies a recording preference (count-in duration) but does not execute code, delete data, or trigger financial transactions. The change is easily reversible by setting a different duration value. It falls under Write category as it changes a configurable setting in the music production software.
From the tool's definition Tool name 'set_count_in_duration' and description 'Set pre-record count-in duration' indicate modification of a recording parameter.
Attacks that exploit this kind of access
The rule that runs set_count_in_duration 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 set_count_in_duration, this is the rule to start with:
set_count_in_duration stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Livepilot, apply this rule, and every set_count_in_duration call is checked against it from then on.
Questions about set_count_in_duration
Set pre-record count-in duration (0-4 bars). It is categorised as a Write tool in the Livepilot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Livepilot MCP server in PolicyLayer and add a rule for set_count_in_duration: 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.
set_count_in_duration is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_count_in_duration 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.
Set action: deny in the PolicyLayer policy for set_count_in_duration. 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.
set_count_in_duration 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.
More on Livepilot, and thousands of servers like it.
This server
Across the catalogue