List all configured SSH connection profiles for remote SLURM clusters.
AI agents call list_ssh_profiles to retrieve information from Srunx without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns existing SSH profile configuration data. It has no side effects, performs no code execution, creates no resources, and modifies nothing. The blast radius of accidental misuse is minimal—at worst an agent gains knowledge of available remote cluster connections, which is informational only.
From the tool's definition Tool name contains 'list' and description states 'List all configured SSH connection profiles' — a pure retrieval operation with no modification, deletion, or execution.
Documented attack patterns abuse exactly the kind of access list_ssh_profiles gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Srunx, and nothing reaches the server without passing your rules. This is the rule we recommend for list_ssh_profiles:
{
"version": "1",
"default": "deny",
"tools": {
"list_ssh_profiles": {}
}
}list_ssh_profiles is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all configured SSH connection profiles for remote SLURM clusters. It is categorised as a Read tool in the Srunx MCP Server, which means it retrieves data without modifying state.
Register the Srunx MCP server in PolicyLayer and add a rule for list_ssh_profiles: 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 Srunx. Nothing to install.
list_ssh_profiles 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 list_ssh_profiles 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 list_ssh_profiles. 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.
list_ssh_profiles is provided by the Srunx MCP server (ksterx/srunx). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Srunx, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
14 Srunx tools catalogued and risk-classified — across an index of 43,000+ MCP servers.