Enable a data link.
AI agents invoke enable_link to trigger actions in Yamcs MCP Server. 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.
Enabling a data link is an operational action that changes the state of an external communication channel in a mission control system. It is not a simple read or write of data, but an execution of a system-level operation that can have significant downstream effects (e.g., initiating data flow, activating spacecraft communication). It falls under Execute as it triggers an external operation.
From the tool's definition 'Enable a data link' — activates an external data link in a mission control system, triggering an operational change to the system's connectivity state
Attacks that exploit this kind of access
Enable a data link. It is categorised as a Execute tool in the Yamcs MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Yamcs MCP Server MCP server in PolicyLayer and add a rule for enable_link: 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.
enable_link 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 enable_link 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 enable_link. 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.
enable_link 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 →