# fl_rename_pattern

A write tool on the FL Studio MCP Server MCP server.

Agent View of the PolicyLayer registry record for `fl_rename_pattern`. HTML page: https://policylayer.com/tools/404kidwiz-fl-studio-mcp/fl-rename-pattern

## Facts

- Tool: `fl_rename_pattern`
- Server: FL Studio MCP Server (`404kidwiz/fl-studio-mcp`) — https://policylayer.com/tools/404kidwiz-fl-studio-mcp.md
- Homepage: https://github.com/404kidwiz/fl-studio-mcp
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "fl_rename_pattern",
    "arguments": {}
  }
}
```

## Why fl_rename_pattern is rated Medium

Renaming a pattern in FL Studio modifies metadata reversibly without executing code or deleting data. This is a typical Write operation (modify data reversibly). Severity is low because renaming has minimal blast radius—it affects only the named pattern's label and is easily undone. The empty description lowers confidence slightly, but the tool name and context make the classification clear.

From the tool's own definition: "Tool name 'fl_rename_pattern' indicates modification of pattern metadata (renaming). The sibling tools on this FL Studio MCP server include operations like fl_add_chord_progression, fl_add_marker, fl_clear_pattern, and fl_auto_mix, which are all…"

## Use case

AI agents use fl_rename_pattern to create or update resources in FL Studio MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FL Studio MCP Server environment.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches FL Studio MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "fl_rename_pattern": {
      "limits": [
        {
          "counter": "fl_rename_pattern_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on FL Studio MCP Server (109)

- `fl_clear_pattern` — Destructive — https://policylayer.com/tools/404kidwiz-fl-studio-mcp/fl-clear-pattern.md
- `fl_delete_marker` — Destructive — https://policylayer.com/tools/404kidwiz-fl-studio-mcp/fl-delete-marker.md
- `fl_undo` — Destructive — https://policylayer.com/tools/404kidwiz-fl-studio-mcp/fl-undo.md
- `fl_auto_mix` — Execute — https://policylayer.com/tools/404kidwiz-fl-studio-mcp/fl-auto-mix.md
- `fl_browser_nav` — Execute — https://policylayer.com/tools/404kidwiz-fl-studio-mcp/fl-browser-nav.md
- `fl_click_at` — Execute — https://policylayer.com/tools/404kidwiz-fl-studio-mcp/fl-click-at.md
- `fl_dismiss_popup` — Execute — https://policylayer.com/tools/404kidwiz-fl-studio-mcp/fl-dismiss-popup.md
- `fl_load_plugin` — Execute — https://policylayer.com/tools/404kidwiz-fl-studio-mcp/fl-load-plugin.md
- `fl_load_vst_preset` — Execute — https://policylayer.com/tools/404kidwiz-fl-studio-mcp/fl-load-vst-preset.md
- `fl_master_bus_clipper_optimizer` — Execute — https://policylayer.com/tools/404kidwiz-fl-studio-mcp/fl-master-bus-clipper-optimizer.md
- `fl_multiband_stereo_widener_matrix` — Execute — https://policylayer.com/tools/404kidwiz-fl-studio-mcp/fl-multiband-stereo-widener-matrix.md
- `fl_orchestral_articulation_mapper` — Execute — https://policylayer.com/tools/404kidwiz-fl-studio-mcp/fl-orchestral-articulation-mapper.md
- `fl_panic` — Execute — https://policylayer.com/tools/404kidwiz-fl-studio-mcp/fl-panic.md
- `fl_play_transport` — Execute — https://policylayer.com/tools/404kidwiz-fl-studio-mcp/fl-play-transport.md
- `fl_polyphonic_midi_to_audio_harmonizer` — Execute — https://policylayer.com/tools/404kidwiz-fl-studio-mcp/fl-polyphonic-midi-to-audio-harmonizer.md
- `fl_render_project` — Execute — https://policylayer.com/tools/404kidwiz-fl-studio-mcp/fl-render-project.md
- `fl_resampler_glitch_generator` — Execute — https://policylayer.com/tools/404kidwiz-fl-studio-mcp/fl-resampler-glitch-generator.md
- `fl_reset_ui` — Execute — https://policylayer.com/tools/404kidwiz-fl-studio-mcp/fl-reset-ui.md
- `fl_set_plugin_param` — Execute — https://policylayer.com/tools/404kidwiz-fl-studio-mcp/fl-set-plugin-param.md
- `fl_song_structure_mutator` — Execute — https://policylayer.com/tools/404kidwiz-fl-studio-mcp/fl-song-structure-mutator.md
- `fl_spectral_morphing_engine` — Execute — https://policylayer.com/tools/404kidwiz-fl-studio-mcp/fl-spectral-morphing-engine.md
- `fl_stop_transport` — Execute — https://policylayer.com/tools/404kidwiz-fl-studio-mcp/fl-stop-transport.md
- `fl_ui_navigate` — Execute — https://policylayer.com/tools/404kidwiz-fl-studio-mcp/fl-ui-navigate.md
- `fl_ai_track_sheet_generator` — Read — https://policylayer.com/tools/404kidwiz-fl-studio-mcp/fl-ai-track-sheet-generator.md
- `fl_catalog_vst_preset` — Read — https://policylayer.com/tools/404kidwiz-fl-studio-mcp/fl-catalog-vst-preset.md
- `fl_get_channel_count` — Read — https://policylayer.com/tools/404kidwiz-fl-studio-mcp/fl-get-channel-count.md
- `fl_get_context` — Read — https://policylayer.com/tools/404kidwiz-fl-studio-mcp/fl-get-context.md
- `fl_get_current_pattern` — Read — https://policylayer.com/tools/404kidwiz-fl-studio-mcp/fl-get-current-pattern.md
- `fl_get_marker` — Read — https://policylayer.com/tools/404kidwiz-fl-studio-mcp/fl-get-marker.md
- `fl_get_mixer_state` — Read — https://policylayer.com/tools/404kidwiz-fl-studio-mcp/fl-get-mixer-state.md
- …and 79 more: https://policylayer.com/tools/404kidwiz-fl-studio-mcp.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=404kidwiz-fl-studio-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/404kidwiz-fl-studio-mcp
