list_spice_missions
AI agents call list_spice_missions to retrieve information from XHelio-SPICE without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to retrieve or enumerate available SPICE missions from the server's registry. Listing operations are read-only with no data modification, deletion, or external execution. The low severity reflects minimal blast radius—incorrect parameters would only return limited or empty results. Confidence is slightly reduced due to the absent description, but the 'list' verb strongly indicates a read operation.
From the tool's definition Tool name 'list_spice_missions' indicates a listing/query operation. No description provided, but the verb 'list' combined with the server's context (managing SPICE kernels for spacecraft ephemeris) suggests retrieval of mission metadata without side effects.
Attacks that exploit this kind of access
list_spice_missions. It is categorised as a Read tool in the XHelio-SPICE MCP Server, which means it retrieves data without modifying state.
Register the XHelio-SPICE MCP server in PolicyLayer and add a rule for list_spice_missions: 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.
list_spice_missions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_spice_missions 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.
Set action: deny in the PolicyLayer policy for list_spice_missions. 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.
list_spice_missions 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →