List all Java processes on the remote server.
AI agents call list_java_processes to retrieve information from Arthas MCP Proxy without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs process enumeration/discovery, which is a read operation. It retrieves information about running Java processes without modifying system state, executing arbitrary commands, or triggering side effects. Even in the context of Arthas diagnostics, this specific tool is limited to listing processes, not executing diagnostic operations on them.
From the tool's definition Tool lists Java processes on remote server; this is a read-only query operation that retrieves process information with no modification, deletion, or execution of code.
Attacks that exploit this kind of access
List all Java processes on the remote server. It is categorised as a Read tool in the Arthas MCP Proxy MCP Server, which means it retrieves data without modifying state.
Register the Arthas MCP Proxy MCP server in PolicyLayer and add a rule for list_java_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 Arthas MCP Proxy. Nothing to install.
list_java_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 list_java_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 list_java_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.
list_java_processes is provided by the Arthas MCP Proxy MCP server (narcissux/arthas-mcp-proxy). 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 →