java_list_processes
AI agents call java_list_processes to retrieve information from Heap Seance without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Listing processes is a retrieval operation with no side effects. It queries system state to enumerate running Java processes, consistent with a diagnostic/investigative tool. Matches the 'Read' category (list operation). Severity is low because process listings do not modify state and expose only metadata about running processes.
From the tool's definition Tool name 'java_list_processes' indicates it lists Java processes. Sibling tools on the server (java_async_alloc_profile, java_class_histogram, java_gc_snapshot, java_heap_dump, java_jfr_start, java_jfr_summary, java_mat_suspects) are all…
Attacks that exploit this kind of access
java_list_processes. It is categorised as a Read tool in the Heap Seance MCP Server, which means it retrieves data without modifying state.
Register the Heap Seance MCP server in PolicyLayer and add a rule for java_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 Heap Seance. Nothing to install.
java_list_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 java_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.
Set action: deny in the PolicyLayer policy for java_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.
java_list_processes is provided by the Heap Seance MCP server (segfaultsorcerer/heap-seance). 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 →