This record as markdown: /tools/funny-booth-aos-mcp-server/create-kpi-metric.md
What create_kpi_metric does on Aos
AI agents use create_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 |
|---|---|---|---|
name | string | Yes | 指標名 |
unit | string | — | |
team_id | string | — | 対象チームID（省略時はユーザーの既定チーム） |
owner_id | string | — | 責任メンバーID（省略時は既定メンバー） |
is_active | boolean | — | |
target_value | number | Yes | 目標値 |
target_direction | string | — | 目標方向（既定 gte） |
Parameters from the server's own tool schema.
Why create_kpi_metric is rated Medium
The tool creates a new KPI metric, which is a reversible data modification operation. This fits the Write category (creates data). Severity is medium because KPI metrics are typically important business metrics—creating incorrect or malicious metrics could affect business decisions and analytics, but the operation is reversible through deletion.
From the tool's definition Tool name 'create_kpi_metric' indicates data creation. Sibling tools on the server include create_* operations (create_task, create_issue, create_team, etc.), establishing a pattern of Write operations. Description is empty, limiting precision.
Attacks that exploit this kind of access
The rule that runs create_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 create_kpi_metric, this is the rule to start with:
create_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 create_kpi_metric call is checked against it from then on.
Questions about create_kpi_metric
create_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.
create_kpi_metric accepts 7 parameters: name, unit, team_id, owner_id, is_active, target_value, target_direction. Required: name, target_value. 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 create_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.
create_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 create_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 create_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.
create_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