This record as markdown: /tools/funny-booth-aos-mcp-server/log-activity.md
What log_activity does on Aos
AI agents use log_activity to create or update resources in Aos, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Aos environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
date | string | — | 対象日 YYYY-MM-DD（省略時は今日） |
task_id | string | — | |
team_id | string | — | 対象チームID（省略時はユーザーの既定チーム） |
member_id | string | — | |
description | string | Yes | 活動内容 |
duration_min | number | — | 所要時間（分） |
Parameters from the server's own tool schema.
Why log_activity is rated Medium
The tool name 'log_activity' indicates recording or creating activity logs, which is a write operation (creating new records). While logging itself is typically safe, in a context with create_* operations it likely modifies a data store. Severity is medium because logging activity typically has limited blast radius unless activity logs are later used for access control or financial records.
From the tool's definition Tool name 'log_activity' suggests creating or recording activity records. Sibling tools on the server include 'create_task', 'create_issue', 'create_todo', and other creation operations, indicating this server manages project/team data.
Attacks that exploit this kind of access
The rule that runs log_activity safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For log_activity, this is the rule to start with:
log_activity 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 Aos, apply this rule, and every log_activity call is checked against it from then on.
Questions about log_activity
log_activity is a write tool on the Aos MCP server. It is categorised as a Write tool in the Aos MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
log_activity accepts 6 parameters: date, task_id, team_id, member_id, description, duration_min. Required: description. The full parameter table on this page comes from the server's own tool schema.
Register the Aos MCP server in PolicyLayer and add a rule for log_activity: 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 Aos. Nothing to install.
log_activity 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_activity 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_activity. 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_activity is provided by the Aos MCP server (@funny-booth/aos-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aos, and thousands of servers like it.
This server
Across the catalogue