Get the full details of a fact by its ID. Use this to retrieve specific fact details when the user asks about a particular fact. You can use the list-all-user-facts tool to get the id of the fact you want to look up.
AI agents call get-user-fact 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 performs a simple lookup/retrieval of existing data (fact details) without creating, modifying, or deleting anything. It is a pure Read operation. The severity is low because retrieving personal facts from a wearable device poses minimal risk compared to Write or Destructive operations; the main concern would be exposure of sensitive personal data, but the agent is operating within the user's own Bee…
From the tool's definition Tool retrieves specific fact details by ID using 'Get the full details of a fact' — a query operation with no modification, deletion, or side effects.
Documented attack patterns abuse exactly the kind of access get-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 get-user-fact:
{
"version": "1",
"default": "deny",
"tools": {
"get-user-fact": {}
}
}get-user-fact 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.
Get the full details of a fact by its ID. Use this to retrieve specific fact details when the user asks about a particular fact. You can use the list-all-user-facts tool to get the id of the fact you want to look up. 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 get-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.
get-user-fact 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 get-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 get-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.
get-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.