Mark a fact as confirmed. Use this to update the confirmation status of a fact based on user feedback. Set confirmed to true if the user has explicitly confirmed the fact, otherwise if it
AI agents use confirm-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 modifies data state (confirmation status) without permanently deleting or irreversibly destroying it. The change can be reverted by calling the tool again with the opposite confirmation value. It lacks the autonomy of Execute (no code/command execution), financial impact, or destructive intent. Write is the appropriate category for state mutations that are reversible.
From the tool's definition The tool updates the confirmation status of a fact ("Mark a fact as confirmed", "update the confirmation status"), which is a reversible modification of existing data.
Documented attack patterns abuse exactly the kind of access confirm-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 confirm-user-fact:
{
"version": "1",
"default": "deny",
"tools": {
"confirm-user-fact": {
"limits": [
{
"counter": "confirm-user-fact_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}confirm-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.
Mark a fact as confirmed. Use this to update the confirmation status of a fact based on user feedback. Set confirmed to true if the user has explicitly confirmed the fact, otherwise if it. 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 confirm-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.
confirm-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 confirm-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 confirm-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.
confirm-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.