This record as markdown: /tools/funny-booth-aos-mcp-server/create-task.md
What create_task does on Aos
AI agents use create_task 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 | Yes | 対象日 YYYY-MM-DD |
title | string | Yes | タスク名 |
rock_id | string | — | 紐づくミッション/バックログID |
team_id | string | — | 対象チームID（省略時はユーザーの既定チーム） |
assignee_id | string | — | 担当メンバーID |
description | string | — |
Parameters from the server's own tool schema.
Why create_task is rated Medium
The tool creates (writes) new task data. This is reversible via deletion and has no direct financial impact or destructive side effects. Severity is medium because creating tasks in a management system could trigger downstream workflows or affect team planning, but the operation itself is non-destructive and controlled.
From the tool's definition Tool name 'create_task' indicates creation of new data (task). Related sibling tools on the same server include create_issue, create_todo, create_backlog_item, which are all Write operations.
Attacks that exploit this kind of access
The rule that runs create_task 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 create_task, this is the rule to start with:
create_task 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 create_task call is checked against it from then on.
Questions about create_task
create_task 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.
create_task accepts 6 parameters: date, title, rock_id, team_id, assignee_id, description. Required: date, title. 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 create_task: 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.
create_task 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 create_task 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 create_task. 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.
create_task 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