Generate polished content: blog posts, SOPs, reports, documentation, whitepapers. Uses the writing-optimized router for best content quality. Specify type, topic, audience, and tone for tailored output.
AI agents use bloom 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.
This tool creates new written content based on user-specified parameters. It has no destructive capability (no deletion or overwrite of existing data), does not execute external code or commands, involves no financial transactions, and does not modify existing data irreversibly. The output is reversible creative content generation, placing it squarely in the Write category.
From the tool's definition Tool description explicitly states it 'Generate[s] polished content: blog posts, SOPs, reports, documentation, whitepapers' and 'Specify type, topic, audience, and tone for tailored output.' The verb 'Generate' and the list of content types (blog posts,…
Documented attack patterns abuse exactly the kind of access bloom 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 bloom:
{
"version": "1",
"default": "deny",
"tools": {
"bloom": {
"limits": [
{
"counter": "bloom_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}bloom 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.
Generate polished content: blog posts, SOPs, reports, documentation, whitepapers. Uses the writing-optimized router for best content quality. Specify type, topic, audience, and tone for tailored output. 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 bloom: 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.
bloom 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 bloom 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 bloom. 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.
bloom 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.