Get the list of allowed read-only commands.
AI agents call ssh_get_allowed_commands to retrieve information from SSH Read-Only 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 about permitted commands—a static configuration query with no ability to modify system state, execute operations, or access sensitive user data directly. The read-only enforcement in the server description and the tool's purpose to list allowed commands (not execute them) place this squarely in the Read category.
From the tool's definition Tool name 'ssh_get_allowed_commands' and description 'Get the list of allowed read-only commands' indicate a query operation that retrieves configuration data without side effects.
Attacks that exploit this kind of access
Get the list of allowed read-only commands. It is categorised as a Read tool in the SSH Read-Only MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SSH Read-Only MCP Server MCP server in PolicyLayer and add a rule for ssh_get_allowed_commands: 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 SSH Read-Only MCP Server. Nothing to install.
ssh_get_allowed_commands 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 ssh_get_allowed_commands 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 ssh_get_allowed_commands. 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.
ssh_get_allowed_commands is provided by the SSH Read-Only MCP Server MCP server (kunwarmahen/ssh-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 →