list_processes

List all running and completed AI agent processes. Returns a simple list with PID, agent type, and status for each process.

Server Agent Bridge lailai258/agent-bridge-mcp
Category Read
Risk class Low
Parameters 00 required

What list_processes does on Agent Bridge

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

Why list_processes needs a policy

This tool retrieves and queries process metadata without side effects. It performs status inspection only, matching the 'Read' category definition of retrieving data without causing side effects. The low severity reflects that process listing poses minimal risk even if misused by an agent, as it only exposes metadata about already-running processes rather than enabling new actions or data loss.

From the tool's definition Tool description explicitly states it 'List all running and completed AI agent processes' and 'Returns a simple list with PID, agent type, and status' — purely informational retrieval with no modification, deletion, or execution capabilities.

Questions about list_processes

What does the list_processes tool do? +

List all running and completed AI agent processes. Returns a simple list with PID, agent type, and status for each process. It is categorised as a Read tool in the Agent Bridge MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_processes? +

Register the Agent Bridge MCP server in PolicyLayer and add a rule for list_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 Agent Bridge. Nothing to install.

What risk level is list_processes? +

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

Can I rate-limit list_processes? +

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

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

list_processes is provided by the Agent Bridge MCP server (lailai258/agent-bridge-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.