get_command_documentation
AI agents call get_command_documentation to retrieve information from Unix Manual Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves documentation and help information—a pure read operation with no side effects. The server explicitly states it provides 'documentation directly within Claude conversations' without executing the commands themselves.
From the tool's definition Tool name 'get_command_documentation' and server purpose 'retrieve help pages, man pages, and usage information' indicates a read-only operation that queries documentation without executing commands or modifying system state.
Attacks that exploit this kind of access
get_command_documentation. It is categorised as a Read tool in the Unix Manual Server MCP Server, which means it retrieves data without modifying state.
Register the Unix Manual Server MCP server in PolicyLayer and add a rule for get_command_documentation: 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 Unix Manual Server. Nothing to install.
get_command_documentation 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 get_command_documentation 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 get_command_documentation. 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.
get_command_documentation is provided by the Unix Manual Server MCP server (tizee/mcp-unix-manual). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_command_documentation is one line of Unix Manual 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 →