Create a new Cycloid stack from a blueprint. CRITICAL: When elicitation context (ctx) is provided, the tool will ALWAYS use interactive elicitation to ask for parameters one by one, REGARDLESS of any parameters provided. The LLM should ONLY provide the 'ref' parameter and let elicitation handle t...
Part of the Server server.
Free to start. No card required.
AI agents use CYCLOID_BLUEPRINT_STACK_CREATE to create or modify resources in Server. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call CYCLOID_BLUEPRINT_STACK_CREATE repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Server.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"CYCLOID_BLUEPRINT_STACK_CREATE": {
"limits": [
{
"counter": "cycloid_blueprint_stack_create_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Server policy for all 6 tools.
These attack patterns abuse exactly the kind of access CYCLOID_BLUEPRINT_STACK_CREATE gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Create a new Cycloid stack from a blueprint. CRITICAL: When elicitation context (ctx) is provided, the tool will ALWAYS use interactive elicitation to ask for parameters one by one, REGARDLESS of any parameters provided. The LLM should ONLY provide the 'ref' parameter and let elicitation handle the rest. DO NOT provide name, use_case, or service_catalog_source_canonical when elicitation is available. 🚨 CRITICAL: The LLM should NEVER provide default values, suggestions, or examples. Let the user make their own choices. Do NOT call this tool with guessed parameters.. It is categorised as a Write tool in the Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Server MCP server in PolicyLayer and add a rule for CYCLOID_BLUEPRINT_STACK_CREATE: 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 Server. Nothing to install.
CYCLOID_BLUEPRINT_STACK_CREATE is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the CYCLOID_BLUEPRINT_STACK_CREATE 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 CYCLOID_BLUEPRINT_STACK_CREATE. 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.
CYCLOID_BLUEPRINT_STACK_CREATE is provided by the Server MCP server (https://mcp.cycloid.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 Server 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.