Deploy a directory to Koyeb
AI agents invoke deploy to trigger actions in Koyeb 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 is an Execute operation: it runs a deployment process that builds and deploys code to live infrastructure, with effects that depend on the directory contents and target environment. While not Destructive (deployments are reversible via redeployment or rollback), it is Execute because it triggers external operations whose consequences depend on the deployment payload and could affect running services.
From the tool's definition Tool description states 'Deploy a directory to Koyeb' which triggers external deployment operations. Server description confirms it 'perform[s] resource lifecycle operations' and can deploy code to infrastructure.
Attacks that exploit this kind of access
Deploy a directory to Koyeb. It is categorised as a Execute tool in the Koyeb MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Koyeb MCP Server MCP server in PolicyLayer and add a rule for deploy: 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 Koyeb MCP Server. Nothing to install.
deploy 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 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. 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 is provided by the Koyeb MCP Server MCP server (samihalawa/mcp-server-koyeb). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →