High-risk tools in Ploi MCP Server
10 of the 46 tools in Ploi MCP Server are classified as high risk. This page profiles those tools specifically, with recommended policy actions and the attack patterns that target them.
Every operation listed below is an action PolicyLayer recommends controlling at the transport layer. Open any tool to see the full profile, risk score, and YAML policy snippet.
Tools at high risk
-
create_daemonExecuteCreate a daemon (long-running process) on a server, e.g.
-
deploy_projectExecuteDeploy the current project using .ploi.json config file and wait for completion. Use this when the user says
-
deploy_siteExecuteTrigger deployment for a site and wait for it to complete. Returns status when done.
-
restart_daemonExecuteRestart a daemon (e.g. to pick up new code after a deploy)
-
restart_queueExecuteRestart a queue worker (e.g. to pick up new code after a deploy)
-
restart_serverExecuteRestart a server
-
restart_serviceExecuteRestart a server service (nginx, php-fpm, mysql, redis, supervisor) to apply config changes.
-
run_database_backupExecuteRun an existing database backup configuration now (
-
toggle_daemonExecutePause or unpause a daemon (single toggle — pauses if running, resumes if paused)
-
toggle_queueExecutePause or unpause a queue worker (single toggle — pauses if running, resumes if paused)
Attacks that target this class
High-risk tools in any server share these documented attack patterns. Each links to the full case and the defensive policy.