Flag an unresolved question — something you searched for but couldn\
AI agents use research_gap_add 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 adds/creates entries in the memory system rather than retrieving data (Read), executing external operations (Execute), deleting data (Destructive), or moving money (Financial). It modifies the knowledge base by recording unresolved questions, which is a Write operation.
From the tool's definition Tool name 'research_gap_add' and description 'Flag an unresolved question' indicate the tool creates or adds new records (research gaps) to the memory system. The action is reversible and creates data within the cognitive memory engine.
Documented attack patterns abuse exactly the kind of access research_gap_add 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 research_gap_add:
{
"version": "1",
"default": "deny",
"tools": {
"research_gap_add": {
"limits": [
{
"counter": "research_gap_add_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}research_gap_add 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.
Flag an unresolved question — something you searched for but couldn\. 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 research_gap_add: 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.
research_gap_add 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 research_gap_add 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 research_gap_add. 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.
research_gap_add 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.