This record as markdown: /tools/funny-booth-aos-mcp-server/get-kpi.md
What get_kpi does on Aos
AI agents call get_kpi 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 |
|---|---|---|---|
team_id | string | — | 対象チームID（省略時はユーザーの既定チーム） |
Parameters from the server's own tool schema.
Why get_kpi is rated Low
The 'get_' prefix is strongly associated with read operations that fetch existing data without side effects. Given the context of metric management and lack of any indication of write/execute/destructive capabilities in the name, this is classified as a Read operation with low severity since it only retrieves metrics data.
From the tool's definition Tool name 'get_kpi' indicates retrieval of key performance indicator data with no modification capability. Description is empty, but sibling tools show this server manages tasks, issues, and metrics, suggesting 'get_kpi' retrieves KPI metric data.
Attacks that exploit this kind of access
The rule that runs get_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 get_kpi, this is the rule to start with:
get_kpi 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_kpi call is checked against it from then on.
Questions about get_kpi
get_kpi 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_kpi accepts 1 parameter: 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_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.
get_kpi 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_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 get_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.
get_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