This record as markdown: /tools/funny-booth-aos-mcp-server/update-kpi-metric.md
What update_kpi_metric does on Aos
AI agents use update_kpi_metric 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 |
name | string | — | |
unit | string | null | — | |
owner_id | string | — | |
is_active | boolean | — | |
target_value | number | — | |
target_direction | string | — |
Parameters from the server's own tool schema.
Why update_kpi_metric is rated Medium
The tool modifies existing KPI metric records, making it a Write action. Severity is medium because misuse could corrupt business metrics and reporting systems, but the impact is reversible (can be corrected with another update). Confidence is 0.85 rather than higher due to empty description, but the verb `update` combined with the domain context of KPI management strongly indicates a Write operation.
From the tool's definition Tool name `update_kpi_metric` indicates modification of key performance indicator data. Sibling tools include `create_kpi_metric`, confirming this server manages KPI entities. The `update_` prefix clearly denotes a write operation.
Attacks that exploit this kind of access
The rule that runs update_kpi_metric 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_metric, this is the rule to start with:
update_kpi_metric 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_metric call is checked against it from then on.
Questions about update_kpi_metric
update_kpi_metric 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_metric accepts 7 parameters: id, name, unit, owner_id, is_active, target_value, target_direction. 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_kpi_metric: 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_metric 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_metric 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_metric. 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_metric 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