List all facts the user has recorded. Use this to get an overview of the user
AI agents call list-all-user-facts to retrieve information from BeeMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries user-recorded facts from the Bee wearable system. It has no side effects—it does not create, modify, delete, or execute any operations. The action is purely informational and read-only, fitting the 'Read' category. Severity is low because unauthorized access to personal facts, while privacy-sensitive, does not cause direct harm like financial loss or data destruction.
From the tool's definition Tool name 'list-all-user-facts' and description 'List all facts the user has recorded. Use this to get an overview of the user' indicates retrieval of existing data without modification, deletion, or external operations.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access list-all-user-facts 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 list-all-user-facts:
{
"version": "1",
"default": "deny",
"tools": {
"list-all-user-facts": {}
}
}list-all-user-facts 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.
List all facts the user has recorded. Use this to get an overview of the user. It is categorised as a Read tool in the BeeMCP MCP Server, which means it retrieves data without modifying state.
Register the Bee MCP server in PolicyLayer and add a rule for list-all-user-facts: 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.
list-all-user-facts 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 list-all-user-facts 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 list-all-user-facts. 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.
list-all-user-facts 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.