Use this when the user asks to deploy or publish a website or web app and wants a public URL. Before generating files or calling this tool, you must call get_deploy_instructions and follow its constraints.
Risk signalsAccepts file system path (files[].file) · Accepts raw HTML/template content (files[].content) · High parameter count (20 properties)
Part of the AppDeploy server.
Free to start. No card required.
AI agents invoke deploy_app to trigger processes or run actions in AppDeploy. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
deploy_app can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"deploy_app": {
"limits": [
{
"counter": "deploy_app_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full AppDeploy policy for all 11 tools.
These attack patterns abuse exactly the kind of access deploy_app gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Use this when the user asks to deploy or publish a website or web app and wants a public URL. Before generating files or calling this tool, you must call get_deploy_instructions and follow its constraints.. It is categorised as a Execute tool in the AppDeploy MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AppDeploy MCP server in PolicyLayer and add a rule for deploy_app: 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 AppDeploy. Nothing to install.
deploy_app 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_app 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_app. 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_app is provided by the AppDeploy MCP server (appdeploy/deploy). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 11 AppDeploy tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.