blueprints_install
Run blueprints.install through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/blueprints-install.md
What blueprints_install does on Appaloft
AI agents invoke blueprints_install to trigger actions in Appaloft. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
slug | string | Yes | |
target | object | — | |
profile | string | — | |
variant | string | — | |
acceptedBy | string | — | |
parameters | object | — | |
secretValues | array | — | |
applicationId | string | — | |
idempotencyKey | string | — | |
acknowledgements | array | — | |
dependencyProvisioning | array | — |
Parameters from the server's own tool schema.
Why blueprints_install is rated High
The tool 'runs' an install operation, which executes an installation process on the platform. Installing blueprints likely provisions resources or configures application infrastructure, making it an Execute-category action with high blast radius if misused (unintended installations, resource provisioning). It's not purely Write since it triggers an operational workflow, not just data mutation.
From the tool's definition 'Run blueprints.install through the Appaloft application operation catalog'
Risk signalsHigh parameter count (31 properties)
Attacks that exploit this kind of access
The rule that runs blueprints_install safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Appaloft, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For blueprints_install, this is the rule to start with:
blueprints_install stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Appaloft, apply this rule, and every blueprints_install call is checked against it from then on.
Questions about blueprints_install
Run blueprints.install through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Execute tool in the Appaloft MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
blueprints_install accepts 11 parameters: slug, target, profile, variant, acceptedBy, parameters, secretValues, applicationId, idempotencyKey, acknowledgements, dependencyProvisioning. Required: slug. The full parameter table on this page comes from the server's own tool schema.
Register the Appaloft MCP server in PolicyLayer and add a rule for blueprints_install: 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 Appaloft. Nothing to install.
blueprints_install 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 blueprints_install 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 blueprints_install. 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.
blueprints_install is provided by the Appaloft MCP server (@appaloft/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Appaloft, and thousands of servers like it.
Across the catalogue