Terminates a background JRMP listener process.
AI agents invoke stop_jrmp_listener to trigger actions in Pentester-MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes a command to stop a background process. While it doesn't create, destroy, or modify persistent data structures, it does directly manipulate running processes and system state—a defining characteristic of Execute category. The operation is reversible (the listener can be restarted), so it is not Destructive.
From the tool's definition The tool 'stop_jrmp_listener' terminates a background process. JRMP (Java Remote Method Protocol) listeners are typically used in penetration testing for remote code execution exploitation.
Documented attack patterns abuse exactly the kind of access stop_jrmp_listener gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pentester-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for stop_jrmp_listener:
{
"version": "1",
"default": "deny",
"tools": {
"stop_jrmp_listener": {
"limits": [
{
"counter": "stop_jrmp_listener_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}stop_jrmp_listener stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Terminates a background JRMP listener process. It is categorised as a Execute tool in the Pentester-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Pentester- MCP server in PolicyLayer and add a rule for stop_jrmp_listener: 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 Pentester-MCP. Nothing to install.
stop_jrmp_listener is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the stop_jrmp_listener 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 stop_jrmp_listener. 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.
stop_jrmp_listener is provided by the Pentester- MCP server (halilkirazkaya/pentester-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Pentester-MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
337 Pentester-MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.