Low Risk

ssh_read_audit_log

Read the audit log of all plan lifecycle events in a human-readable format

How to control ssh_read_audit_log ↓

What ssh_read_audit_log does on SSH Remote MCP Server

AI agents call ssh_read_audit_log to retrieve information from SSH Remote MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why ssh_read_audit_log needs a policy

This tool retrieves and displays audit log entries for informational purposes only. It has no side effects, does not execute commands, modify data, delete records, or trigger external operations. While the broader SSH MCP server enables potentially dangerous Execute and Destructive capabilities, this specific tool is limited to querying and displaying existing audit event records in human-readable format.

From the tool's definition Tool name and description: 'Read the audit log' - explicitly uses 'read' verb and retrieves historical event data without modification or execution.

Documented attack patterns abuse exactly the kind of access ssh_read_audit_log gives an agent:

How to control ssh_read_audit_log

PolicyLayer is an MCP gateway — it sits between your AI agents and SSH Remote MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for ssh_read_audit_log:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "ssh_read_audit_log": {}
  }
}

ssh_read_audit_log is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register SSH Remote MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about ssh_read_audit_log

What does the ssh_read_audit_log tool do? +

Read the audit log of all plan lifecycle events in a human-readable format. It is categorised as a Read tool in the SSH Remote MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on ssh_read_audit_log? +

Register the SSH Remote MCP Server MCP server in PolicyLayer and add a rule for ssh_read_audit_log: 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 Remote MCP Server. Nothing to install.

What risk level is ssh_read_audit_log? +

ssh_read_audit_log is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit ssh_read_audit_log? +

Yes. Add a rate_limit block to the ssh_read_audit_log 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.

How do I block ssh_read_audit_log completely? +

Set action: deny in the PolicyLayer policy for ssh_read_audit_log. 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.

What MCP server provides ssh_read_audit_log? +

ssh_read_audit_log is provided by the SSH Remote MCP Server MCP server (nqmn/adremote-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every SSH Remote MCP Server tool call.

Start from SSH Remote MCP Server, 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.

21 SSH Remote MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.