This record as markdown: /tools/io-github-kivanccakmak-yaver/ps-tree.md
What ps_tree does on Yaver
AI agents call ps_tree 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.
Why ps_tree is rated Low
This tool queries system process information for display purposes only. It has no side effects, does not execute code or commands, does not modify system state, and does not create security-relevant changes. The read classification is appropriate for informational system inspection tools in a local development environment.
From the tool's definition Tool name 'ps_tree' and description 'Show process tree' indicate a read-only operation that retrieves and displays process information without modification, deletion, or execution of processes.
Attacks that exploit this kind of access
The rule that runs ps_tree 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_tree, this is the rule to start with:
ps_tree 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_tree call is checked against it from then on.
Questions about ps_tree
Show process tree. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
Register the Yaver MCP server in PolicyLayer and add a rule for ps_tree: 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_tree 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_tree 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_tree. 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_tree 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