New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

add_user_fact

A write tool on the Coach AI MCP server.

SERVERCoach AI SOURCE94aharris/coach-ai
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about add_user_fact

What does the add_user_fact tool do? +

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.

How do I enforce a policy on add_user_fact? +

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.

What risk level is add_user_fact? +

add_user_fact is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_user_fact? +

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.

How do I block add_user_fact completely? +

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.

What MCP server provides add_user_fact? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Coach AI's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.