Low Risk

get_containers_process_trees

Get process trees for multiple containers

How to control get_containers_process_trees ↓

What get_containers_process_trees does on RAD Security

AI agents call get_containers_process_trees to retrieve information from RAD Security without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_containers_process_trees needs a policy

This tool retrieves process tree information from containers—a read-only operation that gathers observability data without side effects. It aligns with the Read category (retrieve/query data) and poses minimal risk in typical misuse scenarios, warranting a 'low' severity rating.

From the tool's definition Tool name 'get_containers_process_trees' with description 'Get process trees for multiple containers' indicates a retrieval operation. The verb 'get' and the absence of any modification, execution, or destructive language confirm this is a query operation.

Documented attack patterns abuse exactly the kind of access get_containers_process_trees gives an agent:

How to control get_containers_process_trees

PolicyLayer is an MCP gateway — it sits between your AI agents and RAD Security, and nothing reaches the server without passing your rules. This is the rule we recommend for get_containers_process_trees:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_containers_process_trees": {}
  }
}

get_containers_process_trees is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register RAD Security — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_containers_process_trees

What does the get_containers_process_trees tool do? +

Get process trees for multiple containers. It is categorised as a Read tool in the RAD Security MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_containers_process_trees? +

Register the RAD Security MCP server in PolicyLayer and add a rule for get_containers_process_trees: 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 RAD Security. Nothing to install.

What risk level is get_containers_process_trees? +

get_containers_process_trees is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_containers_process_trees? +

Yes. Add a rate_limit block to the get_containers_process_trees 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.

How do I block get_containers_process_trees completely? +

Set action: deny in the PolicyLayer policy for get_containers_process_trees. 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.

What MCP server provides get_containers_process_trees? +

get_containers_process_trees is provided by the RAD Security MCP server (rad-security/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every RAD Security tool call.

Start from RAD Security, 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.

55 RAD Security tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.