Break down complex content into structured, reusable knowledge. Supports multiple output structures: outline, taxonomy, checklist, Q&A, decision tree, or auto-detect.
AI agents use decompose to create or update resources in Celiums Memory — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Celiums Memory environment.
The tool creates or modifies data reversibly by decomposing input content into structured formats and storing these as reusable knowledge modules within the cognitive memory engine. This is characteristic of Write operations. While it does not delete or destroy data (not Destructive), execute arbitrary code (not Execute), or move money (not Financial), it clearly creates new knowledge structures.
From the tool's definition Tool description states it breaks down content into 'structured, reusable knowledge' with multiple output structures (outline, taxonomy, checklist, Q&A, decision tree). This involves creating and storing new knowledge artifacts within the memory system.
Documented attack patterns abuse exactly the kind of access decompose gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Celiums Memory, and nothing reaches the server without passing your rules. This is the rule we recommend for decompose:
{
"version": "1",
"default": "deny",
"tools": {
"decompose": {
"limits": [
{
"counter": "decompose_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}decompose 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.
Free to start. No card required.
Break down complex content into structured, reusable knowledge. Supports multiple output structures: outline, taxonomy, checklist, Q&A, decision tree, or auto-detect. It is categorised as a Write tool in the Celiums Memory MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Celiums Memory MCP server in PolicyLayer and add a rule for decompose: 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 Celiums Memory. Nothing to install.
decompose 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 decompose 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 decompose. 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.
decompose is provided by the Celiums Memory MCP server (terrizoaguimor/celiums-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Celiums Memory, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
62 Celiums Memory tools catalogued and risk-classified — across an index of 43,000+ MCP servers.