Retrieve relevant project rules and context for a query.
AI agents call recall_context to retrieve information from myBrAIn without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves stored project context and rules without modifying, deleting, or executing operations. It is a straightforward read operation that queries persistent memory for informational purposes. The low severity reflects minimal risk even if misused, as retrieval of project context poses no destructive or harmful effects.
From the tool's definition Tool name 'recall_context' and description 'Retrieve relevant project rules and context for a query' indicate data retrieval with no modification or side effects.
Documented attack patterns abuse exactly the kind of access recall_context gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and myBrAIn, and nothing reaches the server without passing your rules. This is the rule we recommend for recall_context:
{
"version": "1",
"default": "deny",
"tools": {
"recall_context": {}
}
}recall_context is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Retrieve relevant project rules and context for a query. It is categorised as a Read tool in the myBrAIn MCP Server, which means it retrieves data without modifying state.
Register the myBrAIn MCP server in PolicyLayer and add a rule for recall_context: 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 myBrAIn. Nothing to install.
recall_context is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the recall_context 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 recall_context. 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.
recall_context is provided by the myBrAIn MCP server (lilium360/mybrain). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from myBrAIn, 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.
5 myBrAIn tools catalogued and risk-classified — across an index of 43,000+ MCP servers.