get_master_meters
Read real-time output meter levels for the master track (left, right, peak).
This record as markdown: /tools/io-github-dreamrec-livepilot/get-master-meters.md
What get_master_meters does on Livepilot
AI agents call get_master_meters 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.
Why get_master_meters is rated Low
This tool retrieves real-time telemetry data (meter levels) from the master track without modifying any state, triggering external operations, or affecting the DAW's project or configuration. It is a pure read operation with no side effects. Severity is low because misuse poses no risk to data integrity, financial systems, or system stability.
From the tool's definition Tool name is 'get_master_meters' and description explicitly states 'Read real-time output meter levels for the master track (left, right, peak).' The verb 'Read' and the passive data retrieval nature (querying current meter levels) with no mention of state…
Attacks that exploit this kind of access
The rule that runs get_master_meters 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 get_master_meters, this is the rule to start with:
get_master_meters is read-only, so it stays allowed. 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 get_master_meters call is checked against it from then on.
Questions about get_master_meters
Read real-time output meter levels for the master track (left, right, peak). It is categorised as a Read tool in the Livepilot MCP Server, which means it retrieves data without modifying state.
Register the Livepilot MCP server in PolicyLayer and add a rule for get_master_meters: 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.
get_master_meters is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_master_meters 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 get_master_meters. 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.
get_master_meters 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