gluecron_refactor_across_repos

Plan + execute a refactor that spans multiple repos owned by the caller. Wraps src/lib/multi-repo-refactor.ts. dry_run: true returns the plan only. Requires 'repo' scope.

SERVERGluecron SOURCEhttps://gluecron.com/mcp

High RISK CLASS

Category Execute

Parameters 31 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-gluecron-gluecron/gluecron-refactor-across-repos.md

WHAT IT DOES

What gluecron_refactor_across_repos does on Gluecron

AI agents invoke gluecron_refactor_across_repos to trigger actions in Gluecron. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Parameter	Type	Required	Description
`dry_run`	boolean	—	When true, returns the plan and does NOT execute.
`description`	string	Yes	Natural-language description
`repository_ids`	array	—	Optional explicit repo IDs to scope the refactor to.

Parameters from the server's own tool schema.

RISK

Why gluecron_refactor_across_repos is rated High

This tool executes a refactoring operation across multiple repositories, which is an execute action that modifies multiple codebases. While it creates/modifies code (Write), the critical aspect is that it EXECUTES a refactoring plan across multiple repos, making it Execute-class. It's not Destructive because refactors are typically reversible through git history, and it's not Financial.

From the tool's definition Plan + execute a refactor that spans multiple repos. The tool performs actual code modifications across repositories (when dry_run is false), making it an execution operation that triggers external code transformation operations whose effects depend on the…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs gluecron_refactor_across_repos safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Gluecron, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gluecron_refactor_across_repos, this is the rule to start with:

gluecron_refactor_across_repos Rate-limited

gluecron_refactor_across_repos stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "gluecron_refactor_across_repos": {
      "limits": [
        {
          "counter": "gluecron_refactor_across_repos_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Gluecron, apply this rule, and every gluecron_refactor_across_repos call is checked against it from then on.

FAQ

Questions about gluecron_refactor_across_repos

What does the gluecron_refactor_across_repos tool do? +

Plan + execute a refactor that spans multiple repos owned by the caller. Wraps src/lib/multi-repo-refactor.ts. dry_run: true returns the plan only. Requires 'repo' scope. It is categorised as a Execute tool in the Gluecron MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does gluecron_refactor_across_repos accept? +

gluecron_refactor_across_repos accepts 3 parameters: dry_run, description, repository_ids. Required: description. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on gluecron_refactor_across_repos? +

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

What risk level is gluecron_refactor_across_repos? +

gluecron_refactor_across_repos is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit gluecron_refactor_across_repos? +

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

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

gluecron_refactor_across_repos is provided by the Gluecron MCP server (https://gluecron.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Gluecron, and thousands of servers like it.

This server

All 60 Gluecron tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →