Check if a command would pass the guardrail safety check WITHOUT executing it.
AI agents call validate_command_safety to retrieve information from Post-Exploitation tmux MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool only inspects whether a command would be permitted by the safety guardrails—it performs no execution, modification, deletion, or other action. It is purely informational. Even though the server manages tmux sessions and execution contexts, this specific tool is a safety checker that reads/evaluates policy compliance without triggering any operations.
From the tool's definition Tool name explicitly states 'validate' and description says 'Check if a command would pass' and 'WITHOUT executing it.' This is a read operation that queries the state of guardrails without side effects.
Attacks that exploit this kind of access
Check if a command would pass the guardrail safety check WITHOUT executing it. It is categorised as a Read tool in the Post-Exploitation tmux MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Post-Exploitation tmux MCP Server MCP server in PolicyLayer and add a rule for validate_command_safety: 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 Post-Exploitation tmux MCP Server. Nothing to install.
validate_command_safety 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 validate_command_safety 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 validate_command_safety. 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.
validate_command_safety is provided by the Post-Exploitation tmux MCP Server MCP server (raghavansv/tmux-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
validate_command_safety is one line of Post-Exploitation tmux MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →