This record as markdown: /tools/funny-booth-aos-mcp-server/get-missions.md
What get_missions does on Aos
AI agents call get_missions to retrieve information from Aos without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
quarter | string | — | 四半期（例 2026-Q3） |
team_id | string | — | 対象チームID（省略時はユーザーの既定チーム） |
Parameters from the server's own tool schema.
Why get_missions is rated Low
The 'get_' prefix strongly indicates a read-only retrieval operation. Despite the lack of explicit description, the tool's name and context within a project/task management server (evidenced by sibling tools for creating missions, tasks, todos, issues, etc.) clearly point to a data retrieval function.
From the tool's definition Tool name 'get_missions' indicates a retrieval operation. No description provided, but the naming pattern (get_*) alongside sibling tools like create_mission, create_task, create_todo suggests this queries existing mission data without modification.
Attacks that exploit this kind of access
The rule that runs get_missions 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 get_missions, this is the rule to start with:
get_missions is read-only, so it stays allowed. 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 get_missions call is checked against it from then on.
Questions about get_missions
get_missions is a read tool on the Aos MCP server. It is categorised as a Read tool in the Aos MCP Server, which means it retrieves data without modifying state.
get_missions accepts 2 parameters: quarter, team_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 get_missions: 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.
get_missions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_missions 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 get_missions. 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.
get_missions 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