This record as markdown: /tools/94aharris-coach-ai/add-user-fact.md
What add_user_fact does on Coach AI
AI agents use add_user_fact to create or update resources in Coach AI, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Coach AI environment.
Why add_user_fact is rated Medium
The tool creates or modifies user profile data in the persistent memory system. While the description is empty, the name combined with server context and sibling tool patterns clearly indicates this is a Write operation that adds factual information about the user.
From the tool's definition Tool name 'add_user_fact' indicates data creation/modification. Sibling tools on the server include 'add_task_context', 'add_todo', 'create_daily_note', 'complete_todo', and 'delete_todo', establishing a pattern of data manipulation operations.
Attacks that exploit this kind of access
The rule that runs add_user_fact safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Coach AI, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For add_user_fact, this is the rule to start with:
add_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Coach AI, apply this rule, and every add_user_fact call is checked against it from then on.
Questions about add_user_fact
add_user_fact is a write tool on the Coach AI MCP server. It is categorised as a Write tool in the Coach AI MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Coach AI MCP server in PolicyLayer and add a rule for add_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 Coach AI. Nothing to install.
add_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 add_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 add_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.
add_user_fact is provided by the Coach AI MCP server (94aharris/coach-ai). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Coach AI, and thousands of servers like it.
This server
Across the catalogue