start_listener blocked Agent's MCP calling #6

New Issue

2026-02-27T13:57:40-05:00

yindo commented

2026-02-27 13:57:40 -05:00

Originally created by @DullJZ on GitHub (Jul 13, 2025).

start_listener function exhibits a behavior where it waits for 60 seconds after starting a listener job to poll for new sessions, which results in Agent waiting for a result from MCP.

Actually, an exploit such as linux/x86/meterpreter/reverse_tcp can take more than 60 seconds to be executed in the target through phishing. Setting start_listener to non-blocking mode and using another function to check if there is a new session to establish a connection may be a better choice

Originally created by @DullJZ on GitHub (Jul 13, 2025). `start_listener` function exhibits a behavior where it waits for 60 seconds after starting a listener job to poll for new sessions, which results in Agent waiting for a result from MCP. Actually, an exploit such as `linux/x86/meterpreter/reverse_tcp` can take more than 60 seconds to be executed in the target through phishing. Setting `start_listener` to non-blocking mode and using another function to check if there is a new session to establish a connection may be a better choice

yindo closed this issue

2026-02-27 13:57:40 -05:00

yindo commented

2026-02-27 13:57:40 -05:00