apply_manifest

Apply Kubernetes manifest to cluster

SERVERNcp SOURCE@portel/ncp

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/io-github-portel-dev-ncp/apply-manifest.md

WHAT IT DOES

What apply_manifest does on Ncp

AI agents invoke apply_manifest to trigger actions in Ncp. 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 apply_manifest is rated High

Applying a Kubernetes manifest can create, update, or replace any cluster resource (Deployments, Services, RBAC rules, etc.), triggering real infrastructure changes. It is not purely Write because it executes against a live cluster with immediate operational effects. Misuse could expose services, escalate privileges, or destabilize workloads, making severity high.

From the tool's definition 'Apply Kubernetes manifest to cluster' — applying a manifest triggers external operations that create, modify, or reconfigure live cluster resources

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs apply_manifest safely

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

apply_manifest Rate-limited

apply_manifest 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": {
    "apply_manifest": {
      "limits": [
        {
          "counter": "apply_manifest_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 Ncp, apply this rule, and every apply_manifest call is checked against it from then on.

FAQ

Questions about apply_manifest

What does the apply_manifest tool do? +

Apply Kubernetes manifest to cluster. It is categorised as a Execute tool in the Ncp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on apply_manifest? +

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

What risk level is apply_manifest? +

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

Can I rate-limit apply_manifest? +

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

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

apply_manifest is provided by the Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ncp, and thousands of servers like it.

This server

All 275 Ncp 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 →