list_active_processes

List all active processes on the PengStrike AI server.

SERVERPengstrike SOURCEwangqiongpeng/pengstrike-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/pengstrike-mcp/list-active-processes.md

WHAT IT DOES

What list_active_processes does on Pengstrike

AI agents call list_active_processes to retrieve information from Pengstrike without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_active_processes is rated Low

Even though list_active_processes only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_active_processes safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Pengstrike, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_active_processes, this is the rule to start with:

list_active_processes Allowed

list_active_processes is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_active_processes": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Pengstrike, apply this rule, and every list_active_processes call is checked against it from then on.

FAQ

Questions about list_active_processes

What does the list_active_processes tool do? +

List all active processes on the PengStrike AI server. It is categorised as a Read tool in the Pengstrike MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_active_processes? +

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

What risk level is list_active_processes? +

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

Can I rate-limit list_active_processes? +

Yes. Add a rate_limit block to the list_active_processes 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 list_active_processes completely? +

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

list_active_processes is provided by the Pengstrike MCP server (wangqiongpeng/pengstrike-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Pengstrike, and thousands of servers like it.

This server

All 163 Pengstrike tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →