Publish an Ethics Calibrated Profile (R5 + 2 approvers). Signing key is
AI agents use profile_publish_secure 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 and publishes profile data with cryptographic signing, making it a Write operation with elevated severity due to the governance controls (approvers, signing keys) and the persistent nature of published profiles.
From the tool's definition Tool name includes 'publish' which creates or modifies data. Description states 'Publish an Ethics Calibrated Profile' indicating creation/modification of a profile artifact.
Documented attack patterns abuse exactly the kind of access profile_publish_secure 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 profile_publish_secure:
{
"version": "1",
"default": "deny",
"tools": {
"profile_publish_secure": {
"limits": [
{
"counter": "profile_publish_secure_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}profile_publish_secure 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.
Publish an Ethics Calibrated Profile (R5 + 2 approvers). Signing key is. 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 profile_publish_secure: 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.
profile_publish_secure 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 profile_publish_secure 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 profile_publish_secure. 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.
profile_publish_secure 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.