split_package

Split package into multiple hosting packages

SERVER20i MCP Server SOURCEcbrown35/20i-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cbrown35-20i-mcp/split-package.md

WHAT IT DOES

What split_package does on 20i MCP Server

AI agents invoke split_package to trigger actions in 20i MCP Server. 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.

RISK

Why split_package is rated High

Splitting a package into multiple hosting packages is a structural reconfiguration operation that triggers external operations on the hosting infrastructure. It's not a simple write (it restructures existing packages), not purely destructive (data isn't deleted), but it executes a significant transformation that could have wide-reaching effects on hosted services, billing, and configurations.

From the tool's definition Split package into multiple hosting packages

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs split_package safely

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

split_package Rate-limited

split_package 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": {
    "split_package": {
      "limits": [
        {
          "counter": "split_package_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 20i MCP Server, apply this rule, and every split_package call is checked against it from then on.

FAQ

Questions about split_package

What does the split_package tool do? +

Split package into multiple hosting packages. It is categorised as a Execute tool in the 20i MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on split_package? +

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

What risk level is split_package? +

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

Can I rate-limit split_package? +

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

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

split_package is provided by the 20i MCP Server MCP server (cbrown35/20i-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on 20i MCP Server, and thousands of servers like it.

This server

All 302 20i MCP Server 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 →