Deploy a Modal application using the provided parameters.
AI agents invoke deploy_modal_app to trigger actions in Modal MCP Server. 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.
deploy_modal_app triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
Deploy a Modal application using the provided parameters. It is categorised as a Execute tool in the Modal MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Modal MCP Server MCP server in PolicyLayer and add a rule for deploy_modal_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 Modal MCP Server. Nothing to install.
deploy_modal_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_modal_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_modal_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_modal_app is provided by the Modal MCP Server MCP server (smehmood/modal-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.