This record as markdown: /tools/94aharris-coach-ai/log-accomplishment.md
What log_accomplishment does on Coach AI
AI agents use log_accomplishment 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 log_accomplishment is rated Medium
This tool creates or appends records of user accomplishments in the persistent memory system. It is a write operation that records user data (similar to sibling tools like add_daily_note_section, add_task_context, add_todo, add_user_fact) without destructive capability.
From the tool's definition Tool name 'log_accomplishment' and description 'Log something the user accomplished' indicate a record-creation or data-recording operation. The verb 'log' typically means to record or write data.
Attacks that exploit this kind of access
The rule that runs log_accomplishment 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 log_accomplishment, this is the rule to start with:
log_accomplishment 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 log_accomplishment call is checked against it from then on.
Questions about log_accomplishment
Log something the user accomplished. 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 log_accomplishment: 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.
log_accomplishment 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 log_accomplishment 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 log_accomplishment. 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.
log_accomplishment 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