List space systems from the Mission Database.
AI agents call space_systems to retrieve information from Yamcs MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists space system metadata from a read-only database query. It has no side effects, does not execute commands, does not modify data, and does not create financial obligations. The blast radius of misuse is minimal—an attacker could only gain information about configured space systems, which is non-sensitive operational metadata in a mission control context.
From the tool's definition Tool name is 'space_systems' and description states 'List space systems from the Mission Database' - a query/retrieval operation with no modification or execution capability.
Attacks that exploit this kind of access
List space systems from the Mission Database. It is categorised as a Read tool in the Yamcs MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Yamcs MCP Server MCP server in PolicyLayer and add a rule for space_systems: 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 Yamcs MCP Server. Nothing to install.
space_systems 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 space_systems 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 space_systems. 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.
space_systems is provided by the Yamcs MCP Server MCP server (paulmramirez/yamcs-mcp-server). 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 →