AI agents use add_arrangement_marker to create or update resources in Flai — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Flai environment.
The tool creates or adds a new arrangement marker in FL Studio—a reversible data modification operation. This matches the Write category (creates data). The severity is low because markers are metadata about music arrangement with no destructive or external side effects. Confidence is moderate (0.75) due to the empty description; the classification relies on the tool name and server context.
From the tool's definition Tool name 'add_arrangement_marker' indicates creation of a marker; the 'add_*' prefix and context of an FL Studio music production MCP server suggest data modification. Description is empty.
Attacks that exploit this kind of access
add_arrangement_marker. It is categorised as a Write tool in the Flai MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Flai MCP server in PolicyLayer and add a rule for add_arrangement_marker: 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 Flai. Nothing to install.
add_arrangement_marker 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 add_arrangement_marker 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 add_arrangement_marker. 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.
add_arrangement_marker is provided by the Flai MCP server (kaupau/flai-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →