Critical Risk →

reset_preferences

사용자 선호도 초기화

How to control reset_preferences ↓

AI agents call reset_preferences to permanently remove resources in FL Studio MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

The tool resets/initializes user preferences, which is an irreversible action that overwrites existing preference data. The word '초기화' means 'initialize' or 'reset to default', implying the current preferences are overwritten and cannot be recovered. This fits the Destructive category as it permanently erases user preference data.

From the tool's definition 사용자 선호도 초기화 (translated: 'Initialize/reset user preferences')

Documented attack patterns abuse exactly the kind of access reset_preferences gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and FL Studio MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for reset_preferences:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "reset_preferences"
  ]
}

reset_preferences disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register FL Studio MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the reset_preferences tool do? +

사용자 선호도 초기화. It is categorised as a Destructive tool in the FL Studio MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on reset_preferences? +

Register the FL Studio MCP server in PolicyLayer and add a rule for reset_preferences: 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 FL Studio MCP. Nothing to install.

What risk level is reset_preferences? +

reset_preferences is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit reset_preferences? +

Yes. Add a rate_limit block to the reset_preferences 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 reset_preferences completely? +

Set action: deny in the PolicyLayer policy for reset_preferences. 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 reset_preferences? +

reset_preferences is provided by the FL Studio MCP server (ohhalim/flstudio-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every FL Studio MCP tool call.

Deterministic rules across all 16 FL Studio MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

16 FL Studio MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.