This record as markdown: /tools/funny-booth-aos-mcp-server/update-mission.md
What update_mission does on Aos
AI agents use update_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 |
|---|---|---|---|
id | string | Yes | ミッションID |
title | string | — | |
status | string | — | |
quarter | string | — | |
due_date | string | null | — | YYYY-MM-DD、null でクリア |
owner_id | string | null | — | |
description | string | null | — |
Parameters from the server's own tool schema.
Why update_mission is rated Medium
The tool updates (modifies) mission data reversibly. Without a description, confidence is moderate. The blast radius is medium: incorrect mission updates could misdirect team efforts, but the operation is reversible via another update call. Not Destructive (update ≠ delete), not Execute (no code/command execution evident), not Financial.
From the tool's definition Tool name 'update_mission' indicates modification of data; no destructive or financial operation is named. Sibling tools include create_* and complete_* patterns typical of task/project management systems.
Attacks that exploit this kind of access
The rule that runs update_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 update_mission, this is the rule to start with:
update_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 update_mission call is checked against it from then on.
Questions about update_mission
update_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.
update_mission accepts 7 parameters: id, title, status, quarter, due_date, owner_id, description. Required: id. 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 update_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.
update_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 update_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 update_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.
update_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