Read output from a process session. Use negative lines value to read last N lines. Use clear=true to clear the buffer after reading.
AI agents call read_process_output to retrieve information from OODA Computer Control without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical output from an already-running process without modifying system state, executing new commands, or affecting data persistence. The clear=true option clears the buffer (a non-destructive, reversible action on transient output) rather than deleting persistent data. It is purely informational with no side effects on the underlying system or processes.
From the tool's definition Tool description states it 'Read[s] output from a process session' with options to read last N lines or clear buffer. The verb 'read' and absence of any modification, deletion, or execution language indicate a retrieval operation.
Documented attack patterns abuse exactly the kind of access read_process_output gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OODA Computer Control, and nothing reaches the server without passing your rules. This is the rule we recommend for read_process_output:
{
"version": "1",
"default": "deny",
"tools": {
"read_process_output": {}
}
}read_process_output 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.
Read output from a process session. Use negative lines value to read last N lines. Use clear=true to clear the buffer after reading. It is categorised as a Read tool in the OODA Computer Control MCP Server, which means it retrieves data without modifying state.
Register the OODA Computer Control MCP server in PolicyLayer and add a rule for read_process_output: 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 OODA Computer Control. Nothing to install.
read_process_output 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 read_process_output 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 read_process_output. 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.
read_process_output is provided by the OODA Computer Control MCP server (mnehmos/mnehmos.ooda.mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OODA Computer Control, 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.
99 OODA Computer Control tools catalogued and risk-classified — across an index of 43,000+ MCP servers.