list_coordinate_frames
AI agents call list_coordinate_frames 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.
Listing operations are retrieval-only and cause no side effects. Even without a description, the 'list_' prefix is a reliable signal of Read category behavior. The sibling tools (compute_distance, get_ephemeris, transform_coordinates) are all read-only ephemeris operations, supporting this classification. Severity is low because retrieving metadata about coordinate frames poses minimal risk if misused.
From the tool's definition Tool name 'list_coordinate_frames' indicates a listing/retrieval operation. The description is empty, but the naming convention (list_*) strongly suggests this is a read-only query that returns available coordinate frame definitions without modifying any data.
Attacks that exploit this kind of access
list_coordinate_frames. 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_coordinate_frames: 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_coordinate_frames 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_coordinate_frames 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_coordinate_frames. 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_coordinate_frames 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 →