This record as markdown: /tools/funny-booth-aos-mcp-server/delete-kpi-entry.md
What delete_kpi_entry does on Aos
AI agents call delete_kpi_entry to permanently remove resources in Aos, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | KPI実績ID |
Parameters from the server's own tool schema.
Why delete_kpi_entry is rated Critical
The name unambiguously signals irreversible deletion of data. KPI metrics are typically business-critical measurements used for tracking and decision-making. Deletion of entries cannot be undone without backup/recovery procedures outside the tool's scope. While severity is not 'critical' (as it's scoped to KPI entries rather than all data), the destructive nature and potential business impact warrant 'high' severity.
From the tool's definition Tool name 'delete_kpi_entry' explicitly indicates deletion of KPI (Key Performance Indicator) entries; no description provided to suggest reversibility or safeguards.
Attacks that exploit this kind of access
The rule that runs delete_kpi_entry 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 delete_kpi_entry, this is the rule to start with:
delete_kpi_entry is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Aos, apply this rule, and every delete_kpi_entry call is checked against it from then on.
Questions about delete_kpi_entry
delete_kpi_entry is a destructive tool on the Aos MCP server. It is categorised as a Destructive tool in the Aos MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_kpi_entry accepts 1 parameter: id. 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 delete_kpi_entry: 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.
delete_kpi_entry is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_kpi_entry 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 delete_kpi_entry. 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.
delete_kpi_entry 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.
Across the catalogue