manage_kernels · XHelio-SPICE MCP: Risk & Policy

WHAT IT DOES

What manage_kernels does on XHelio-SPICE

AI agents use manage_kernels to create or update resources in XHelio-SPICE — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your XHelio-SPICE environment.

WHY IT NEEDS A POLICY

Why manage_kernels needs a policy

SPICE kernels are configuration/data files that define spacecraft positions and orientations. Managing them likely involves uploading, updating, or modifying these files, which constitutes Write-category operations with reversible side effects.

From the tool's definition Tool name 'manage_kernels' combined with server's stated function of 'auto-managed SPICE kernels' suggests creation, modification, or administration of kernel data files. The description is empty, limiting certainty.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

manage_kernels Rate-limited

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

View as policy code

policy.json

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

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches XHelio-SPICE, so you can run agents against it safely.

FAQ

Questions about manage_kernels

What does the manage_kernels tool do? +

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

How do I enforce a policy on manage_kernels? +

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

What risk level is manage_kernels? +

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

Can I rate-limit manage_kernels? +

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

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

manage_kernels is provided by the XHelio-SPICE MCP server (xhelio-spice). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

manage_kernels is one line of XHelio-SPICE's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →