AI agents call list_java_processes to retrieve information from JVM MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays information about running Java processes. It is a read-only operation with no side effects, no code execution, and no data modification. The blast radius is minimal—an agent listing processes could gather intelligence about what JVMs are running, but cannot directly affect system state or security posture.
From the tool's definition Tool name 'list_java_processes' and description 'List all Java processes' indicate a query/enumeration operation that retrieves process information without modifying or executing anything.
Documented attack patterns abuse exactly the kind of access list_java_processes gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and JVM MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_java_processes:
{
"version": "1",
"default": "deny",
"tools": {
"list_java_processes": {}
}
}list_java_processes is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all Java processes. It is categorised as a Read tool in the JVM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the JVM MCP Server 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 JVM MCP Server. 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 JVM MCP Server MCP server (xzq-xu/jvm-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 15 JVM MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
15 JVM MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.