Get comprehensive information about a Yamcs instance.
AI agents call describe_instance 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 queries information about a Yamcs mission control instance. It performs no side effects, data modification, or destructive operations. However, classified as medium severity rather than low because mission control systems are critical infrastructure—unauthorized information disclosure about instance configuration, state, or capabilities could enable further attacks or operational disruption,…
From the tool's definition Tool name 'describe_instance' and description 'Get comprehensive information about a Yamcs instance' indicate retrieval of instance metadata and configuration data without modification.
Attacks that exploit this kind of access
Get comprehensive information about a Yamcs instance. 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 describe_instance: 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.
describe_instance 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 describe_instance 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 describe_instance. 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.
describe_instance 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 →