migrate_config

THE RISK

Medium Risk

Why migrate_config needs a policy

Migration of a configuration typically means transforming an existing config to a newer format and writing it back, which is a reversible write operation. The sibling tools include 'write_config' as a separate tool, but migration likely applies changes to the config file. The description is truncated so confidence is reduced.

From the tool's definition Tool name 'migrate_config' and partial description 'Apply Renovate' — description is truncated/uninformative

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

POLICY

How to control migrate_config

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

policy.json

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

migrate_config 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 Renovate — 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 Renovate tools

Execute dry_run Run Renovate in dry-run mode to preview what it would do — no PRs opened, no git pushes. R Write write_config Write a Renovate config to disk. Runs renovate-config-validator first — refuses to write i Read dry_run_diff Compute a semantic diff between two Read lint_config Run a semantic lint pass over a Renovate config. Complements validate_config: schema valid Read check_setup Report whether the Renovate CLI and config validator are reachable, their versions, and an Read explain_config Inverse of resolve_config: walk the same preset tree, but annotate every leaf field with t Read get_version Report the renovate-mcp server version and whether it Read read_config Locate and parse the Renovate configuration in a repository. Searches for renovate.json, r

All 11 Renovate 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 migrate_config

What does the migrate_config tool do? +

Apply Renovate. It is categorised as a Write tool in the Renovate MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on migrate_config? +

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

What risk level is migrate_config? +

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

Can I rate-limit migrate_config? +

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

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

migrate_config is provided by the Renovate MCP server (renovate-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Renovate tool call.

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

CHECK YOUR STACK →