This record as markdown: /tools/funny-booth-aos-mcp-server/update-strategy.md
What update_strategy does on Aos
AI agents use update_strategy 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 |
|---|---|---|---|
team_id | string | — | 対象チームID（省略時はユーザーの既定チーム） |
core_values | array | — | |
one_year_plan | object | — | 1年計画（任意JSON） |
ten_year_target | string | null | — | |
core_focus_niche | string | null | — | |
marketing_target | string | null | — | |
marketing_uniques | array | — | |
core_focus_purpose | string | null | — | |
three_year_picture | object | — | 3年ピクチャー（任意JSON） |
marketing_guarantee | string | null | — | |
marketing_proven_process | string | null | — |
Parameters from the server's own tool schema.
Why update_strategy is rated Medium
The verb 'update' signals reversible modification rather than deletion or financial impact. Without a description, confidence is moderate. The tool likely updates strategy records in a project management system (given sibling tools like create_task, create_mission, create_team). Update operations are Write category.
From the tool's definition Tool name 'update_strategy' indicates modification of strategy data. Sibling tools on this server include create_* and complete_* operations, suggesting a project/task management context where 'update_strategy' would reversibly modify configuration or…
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs update_strategy 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_strategy, this is the rule to start with:
update_strategy 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_strategy call is checked against it from then on.
Questions about update_strategy
update_strategy 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_strategy accepts 11 parameters: team_id, core_values, one_year_plan, ten_year_target, core_focus_niche, marketing_target, marketing_uniques, core_focus_purpose, three_year_picture, marketing_guarantee, marketing_proven_process. 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_strategy: 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_strategy 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_strategy 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_strategy. 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_strategy 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