transform_coordinates
AI agents invoke transform_coordinates to trigger actions in XHelio-SPICE. 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.
Transform operations execute mathematical transformations whose output depends on supplied arguments (coordinate frames, epochs, spacecraft state). This fits the Execute category: it runs computations triggered by arguments, though results are deterministic read-only outputs without side effects on the underlying system.
From the tool's definition Tool name is 'transform_coordinates' with empty description. Context indicates this is part of a SPICE kernel system for spacecraft ephemeris.
Attacks that exploit this kind of access
transform_coordinates. It is categorised as a Execute tool in the XHelio-SPICE MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the XHelio-SPICE MCP server in PolicyLayer and add a rule for transform_coordinates: 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.
transform_coordinates is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the transform_coordinates 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 transform_coordinates. 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.
transform_coordinates 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 →