This record as markdown: /tools/io-github-kivanccakmak-yaver/ps-aux.md
What ps_aux does on Yaver
AI agents call ps_aux to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
sort | string | — | cpu or mem |
filter | string | — | Filter by process name |
Parameters from the server's own tool schema.
Why ps_aux is rated Low
This tool retrieves and queries system process data without side effects. While process listing could theoretically expose sensitive information about running applications, it is fundamentally a read-only query operation. The sorting and filtering options are passive transformations of retrieved data. No execution, write, deletion, or financial operations are involved.
From the tool's definition Tool name 'ps_aux' and description 'List processes' indicate read-only retrieval of process information with optional sorting/filtering. No modification, deletion, or execution capabilities mentioned.
Attacks that exploit this kind of access
The rule that runs ps_aux safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ps_aux, this is the rule to start with:
ps_aux is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every ps_aux call is checked against it from then on.
Questions about ps_aux
List processes. Sort by cpu/mem, or filter by name. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
ps_aux accepts 2 parameters: sort, filter. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for ps_aux: 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 Yaver. Nothing to install.
ps_aux 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 ps_aux 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 ps_aux. 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.
ps_aux is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue