aasagenticawesomeskills__compose_stack
Build an in-memory Core manifest from exact skill IDs already chosen by Codex or Claude. Call only after the agent has enumerated primary project capabilities, searched and compared candidates for each, covered every capability with at least one non-redundant valid skill or explicitly identified ...
This record as markdown: /tools/ai-rokha-rokha/aasagenticawesomeskills--compose-stack.md
What aasagenticawesomeskills__compose_stack does on Rokha
AI agents use aasagenticawesomeskills__compose_stack to create or update resources in Rokha, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rokha environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | |
profile | object | Yes | |
targets | array | — | |
skillIds | array | Yes |
Parameters from the server's own tool schema.
Why aasagenticawesomeskills__compose_stack is rated Medium
Creates an in-memory manifest artifact; reversible write with no destructive or financial effects.
From the tool's definition Build an in-memory Core manifest from exact skill IDs
Risk signalsAccepts URL/endpoint input (targets[].host) · High parameter count (11 properties) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs aasagenticawesomeskills__compose_stack safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Rokha, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For aasagenticawesomeskills__compose_stack, this is the rule to start with:
aasagenticawesomeskills__compose_stack stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Rokha, apply this rule, and every aasagenticawesomeskills__compose_stack call is checked against it from then on.
Questions about aasagenticawesomeskills__compose_stack
Build an in-memory Core manifest from exact skill IDs already chosen by Codex or Claude. Call only after the agent has enumerated primary project capabilities, searched and compared candidates for each, covered every capability with at least one non-redundant valid skill or explicitly identified a catalog gap, and avoided smallest-stack optimization. Core applies no semantic policy toward small stacks; the maximum of 128 skills per manifest is a technical payload limit. Core verifies catalog membership and preserves the selection without ranking, substitution, policy, or metadata filtering. It is categorised as a Write tool in the Rokha MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
aasagenticawesomeskills__compose_stack accepts 4 parameters: name, profile, targets, skillIds. Required: profile, skillIds. The full parameter table on this page comes from the server's own tool schema.
Register the Rokha MCP server in PolicyLayer and add a rule for aasagenticawesomeskills__compose_stack: 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 Rokha. Nothing to install.
aasagenticawesomeskills__compose_stack 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 aasagenticawesomeskills__compose_stack 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 aasagenticawesomeskills__compose_stack. 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.
aasagenticawesomeskills__compose_stack is provided by the Rokha MCP server (https://rokha.ai/mcp/jsonrpc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Rokha, and thousands of servers like it.
This server
Across the catalogue