This record as markdown: /tools/funny-booth-aos-mcp-server/create-mission.md
What create_mission does on Aos
AI agents use create_mission 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 |
|---|---|---|---|
title | string | Yes | ミッション名 |
status | string | — | |
quarter | string | Yes | 四半期（例 2026-Q3） |
team_id | string | — | 対象チームID（省略時はユーザーの既定チーム） |
due_date | string | — | 期日 YYYY-MM-DD（省略時は四半期末日） |
owner_id | string | — | 担当メンバーID（省略時は既定メンバー） |
description | string | — |
Parameters from the server's own tool schema.
Why create_mission is rated Medium
The 'create_mission' tool most likely creates or adds a mission entity, which is a reversible write operation. Write is the appropriate category. Severity is medium because creating missions could affect organizational planning and workflows, but the operation is reversible.
From the tool's definition Tool name 'create_mission' indicates a creation operation. The sibling tools on this server include multiple create_* and delete_* operations, confirming this is a data manipulation server.
Attacks that exploit this kind of access
The rule that runs create_mission 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_mission, this is the rule to start with:
create_mission 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_mission call is checked against it from then on.
Questions about create_mission
create_mission 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_mission accepts 7 parameters: title, status, quarter, team_id, due_date, owner_id, description. Required: title, quarter. 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_mission: 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_mission 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_mission 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_mission. 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_mission 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