deck_probe
Check SSH connectivity and confirm basic SteamOS/Linux identity.
This record as markdown: /tools/mcp-control-plane/deck-probe.md
What deck_probe does on Mcp Control Plane
AI agents invoke deck_probe to trigger actions in Mcp Control Plane. 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.
Why deck_probe is rated High
Establishing SSH connectivity is an active network operation that triggers an external connection. While it appears read-like (checking/confirming identity), initiating SSH sessions constitutes executing an external operation. Misuse could probe unauthorized systems or reveal network topology. Severity is medium as the action is diagnostic but involves real network access.
From the tool's definition Check SSH connectivity — this tool establishes an SSH connection to a remote system, which is an active external operation beyond simple data retrieval
Attacks that exploit this kind of access
The rule that runs deck_probe safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Control Plane, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For deck_probe, this is the rule to start with:
deck_probe stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Control Plane, apply this rule, and every deck_probe call is checked against it from then on.
Questions about deck_probe
Check SSH connectivity and confirm basic SteamOS/Linux identity. It is categorised as a Execute tool in the Mcp Control Plane MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Control Plane MCP server in PolicyLayer and add a rule for deck_probe: 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 Mcp Control Plane. Nothing to install.
deck_probe 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 deck_probe 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 deck_probe. 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.
deck_probe is provided by the Mcp Control Plane MCP server (albertik322-sudo/mcp-control-plane). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Control Plane, and thousands of servers like it.
Across the catalogue