Get detailed information about a specific command.
AI agents call get_command 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 metadata or details about a command definition without executing it, modifying it, or causing any external effects. It is a straightforward read operation on command information stored in the Yamcs mission control system. No data is created, modified, deleted, or executed.
From the tool's definition Tool name 'get_command' and description 'Get detailed information about a specific command' indicate data retrieval only. The verb 'Get' and phrase 'detailed information' are characteristic of query operations with no side effects.
Attacks that exploit this kind of access
Get detailed information about a specific command. 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 get_command: 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.
get_command 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 get_command 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 get_command. 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.
get_command 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 →