Orchestrate a deployment via @manifest-network/manifest-agent-core.
AI agents invoke deploy_app_orchestrated to trigger actions in Manifest 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 executes deployment operations on external infrastructure (Manifest Network), making it an Execute category risk. It has high severity because deployment orchestration can affect production systems, alter application state, and impact availability.
From the tool's definition Tool name 'deploy_app_orchestrated' and description stating it 'Orchestrate a deployment via @manifest-network/manifest-agent-core' indicates execution of deployment operations with external side effects.
Attacks that exploit this kind of access
Orchestrate a deployment via @manifest-network/manifest-agent-core. It is categorised as a Execute tool in the Manifest MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Manifest MCP server in PolicyLayer and add a rule for deploy_app_orchestrated: 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 Manifest MCP. Nothing to install.
deploy_app_orchestrated 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_orchestrated 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_orchestrated. 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_orchestrated is provided by the Manifest MCP server (manifest-network/manifest-mcp-mono). 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 →