// SCAN REPORT

XHelio-SPICE

6 tools. 2 can modify or destroy data without limits.

2 write tools that can modify data. Rate limits recommended.

Last updated: 1 Jul 2026

2 can modify or destroy data

4 read-only

6 tools total

Community server · catalogue entry verified 01/07/2026

How to control XHelio-SPICE ↓

TOOL MAP

What XHelio-SPICE exposes to your agents

Read (4) Write / Execute (2) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous XHelio-SPICE tools

Execute · Medium transform_coordinates Transform operations execute mathematical transformations whose output depends on supplied arguments (coordinate frames, epochs, spacecraft state). Write · Medium manage_kernels SPICE kernels are configuration/data files that define spacecraft positions and orientations.

2 of XHelio-SPICE's 6 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control XHelio-SPICE

PolicyLayer is an MCP gateway — it sits between your AI agents and XHelio-SPICE, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "manage_kernels": {
    "limits": [
      {
        "counter": "manage_kernels_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "compute_distance": {
    "limits": [
      {
        "counter": "compute_distance_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register XHelio-SPICE — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON XHELIO-SPICE →

Instant setup, no code required.

FULL CATALOGUE

All 6 XHelio-SPICE tools

EXECUTE 1 tools

Execute transform_coordinates transform_coordinates

WRITE 1 tools

Write manage_kernels manage_kernels

READ 4 tools

Read compute_distance compute_distance Read get_ephemeris get_ephemeris Read list_coordinate_frames list_coordinate_frames Read list_spice_missions list_spice_missions

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about XHelio-SPICE

How do I prevent bulk modifications through XHelio-SPICE? +

The XHelio-SPICE server has 1 write tools including manage_kernels. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach XHelio-SPICE.

How many tools does the XHelio-SPICE MCP server expose? +

6 tools across 3 categories: Execute, Read, Write. 4 are read-only. 2 can modify, create, or delete data.

How do I enforce a policy on XHelio-SPICE? +

Register the XHelio-SPICE MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every XHelio-SPICE tool call.

Deterministic rules across all 6 XHelio-SPICE tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON XHELIO-SPICE →

Instant setup, no code required.

6 XHelio-SPICE tools catalogued and risk-classified — across an index of 43,000+ MCP servers.