Create a new fact. Use this to record new information about the user, their preferences, and other details that might be relevant to answering other questions.
AI agents use record-user-fact to create or update resources in BeeMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your BeeMCP environment.
This tool creates and persists new data (user facts) in a reversible manner. It does not execute arbitrary code, delete data irreversibly, or involve financial transactions. The 'Create' operation places it squarely in the Write category.
From the tool's definition Tool description states 'Create a new fact' - explicitly a creation operation that modifies user data by adding new information to the Bee lifelogging system.
Documented attack patterns abuse exactly the kind of access record-user-fact gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and BeeMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for record-user-fact:
{
"version": "1",
"default": "deny",
"tools": {
"record-user-fact": {
"limits": [
{
"counter": "record-user-fact_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}record-user-fact 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.
Create a new fact. Use this to record new information about the user, their preferences, and other details that might be relevant to answering other questions. It is categorised as a Write tool in the BeeMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bee MCP server in PolicyLayer and add a rule for record-user-fact: 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 BeeMCP. Nothing to install.
record-user-fact 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 record-user-fact 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 record-user-fact. 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.
record-user-fact is provided by the Bee MCP server (okgodoit/beemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 19 BeeMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
19 BeeMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.