Deploy to remote, deploy demo, publish demo, upload static site. 部署到远程、部署 demo、发布 demo、上传静态站点。Uses rsync to /var/www/html/demo-remote/{user}/{project}/. For OTP/interactive auth, use session tools (start_deploy_session/poll_deploy_session/submit_deploy_input).
AI agents invoke deploy_static to trigger actions in Remote Demo 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 triggers external operations (rsync deployment) whose effects depend on provided arguments (user, project, directory contents). While ostensibly for deploying static files, rsync execution on remote systems qualifies as Execute rather than Write because it involves shell command execution on external infrastructure.
From the tool's definition Tool performs remote deployment using rsync to /var/www/html/demo-remote/{user}/{project}/, which involves executing external operations (rsync command) on remote hosts.
Attacks that exploit this kind of access
Deploy to remote, deploy demo, publish demo, upload static site. 部署到远程、部署 demo、发布 demo、上传静态站点。Uses rsync to /var/www/html/demo-remote/{user}/{project}/. For OTP/interactive auth, use session tools (start_deploy_session/poll_deploy_session/submit_deploy_input). It is categorised as a Execute tool in the Remote Demo MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Remote Demo MCP server in PolicyLayer and add a rule for deploy_static: 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 Remote Demo MCP. Nothing to install.
deploy_static 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 deploy_static 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 deploy_static. 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.
deploy_static is provided by the Remote Demo MCP server (jake-bcn/remote-demo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
deploy_static is one line of Remote Demo's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →