Get information about running processes
AI agents call get_running_processes to retrieve information from MCP Start App without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves process metadata (names, PIDs, resource usage, etc.) but does not start, stop, modify, or execute processes. It is a passive information-gathering operation analogous to running 'ps' or 'tasklist'. No side effects or destructive potential.
From the tool's definition Tool name and description indicate it 'Get[s] information about running processes' — a read-only retrieval operation with no modification or execution capability.
Attacks that exploit this kind of access
Get information about running processes. It is categorised as a Read tool in the MCP Start App MCP Server, which means it retrieves data without modifying state.
Register the MCP Start App MCP server in PolicyLayer and add a rule for get_running_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 MCP Start App. Nothing to install.
get_running_processes 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 get_running_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.
Set action: deny in the PolicyLayer policy for get_running_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.
get_running_processes is provided by the MCP Start App MCP server (nexus-aissam/mcp-local). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →