This record as markdown: /tools/funny-booth-aos-mcp-server/update-kpi.md
What update_kpi does on Aos
AI agents use update_kpi 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 |
|---|---|---|---|
note | string | — | |
value | number | Yes | 実績値 |
team_id | string | — | 対象チームID（省略時はユーザーの既定チーム） |
metric_id | string | Yes | 指標ID |
week_start | string | Yes | 週の開始日 YYYY-MM-DD |
Parameters from the server's own tool schema.
Why update_kpi is rated Medium
The tool performs a data modification operation (update) on KPI metrics based on its name. Without a detailed description, the exact scope and reversibility cannot be fully determined, but update operations are typically reversible (Write category).
From the tool's definition Tool name is 'update_kpi', suggesting modification of Key Performance Indicator metrics. No description provided. Sibling tools include create_kpi_metric, indicating this server manages organizational metrics and tracking systems.
Attacks that exploit this kind of access
The rule that runs update_kpi 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_kpi, this is the rule to start with:
update_kpi 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_kpi call is checked against it from then on.
Questions about update_kpi
update_kpi 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_kpi accepts 5 parameters: note, value, team_id, metric_id, week_start. Required: value, metric_id, week_start. 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_kpi: 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_kpi 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_kpi 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_kpi. 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_kpi 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