sync_claude_preferences

THE RISK

Medium Risk

Why sync_claude_preferences needs a policy

Syncing preferences involves writing or updating configuration/settings data in Msty to match Claude's preferences (or vice versa). This is a reversible write operation — preferences can typically be changed again. The blast radius is medium since misconfigured preferences could affect AI behavior across sessions, but it's not destructive or financial.

From the tool's definition 'Sync Claude preferences with Msty' — synchronizing preferences implies writing/updating configuration data between Claude and Msty

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

POLICY

How to control sync_claude_preferences

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sync_claude_preferences": {
      "limits": [
        {
          "counter": "sync_claude_preferences_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

sync_claude_preferences 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.

Create a free account and register Msty Admin MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Msty Admin MCP tools

Execute bloom_evaluate_model Run Bloom behavioral evaluation on a model. Execute run_calibration_test Run calibration test on a model. Execute chat_with_llamacpp_model Chat with a LLaMA.cpp model. Execute chat_with_local_model Chat with a Local AI (Ollama) model. Execute chat_with_mlx_model Chat with an MLX model. Write generate_persona Generate AI persona configuration. Write import_tool_config Import tool configuration. Read identify_handoff_triggers Identify handoff trigger patterns.

All 36 Msty Admin MCP tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about sync_claude_preferences

What does the sync_claude_preferences tool do? +

Sync Claude preferences with Msty. It is categorised as a Write tool in the Msty Admin MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on sync_claude_preferences? +

Register the Msty Admin MCP server in PolicyLayer and add a rule for sync_claude_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 Msty Admin MCP. Nothing to install.

What risk level is sync_claude_preferences? +

sync_claude_preferences is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit sync_claude_preferences? +

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

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

sync_claude_preferences is provided by the Msty Admin MCP server (m-pineapple/msty-admin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Msty Admin MCP tool call.

Start from Msty Admin MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →