list_kubernetes_cost_allocations
Query Kubernetes Cost Allocations telemetry data from OneUptime. IMPORTANT: telemetry tables are large — always filter by a time range and keep limits small (e.g. 10-50). Each field accepts a direct value (exact match) or an operator object {"_type": "<Operator>", "value": ...}. Operators: EqualT...
This record as markdown: /tools/com-oneuptime-mcp/list-kubernetes-cost-allocations.md
What list_kubernetes_cost_allocations does on OneUptime
AI agents call list_kubernetes_cost_allocations to retrieve information from OneUptime 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 |
|---|---|---|---|
skip | number | — | Number of records to skip. Default: 0. |
sort | object | — | Sort order. Use "ASC" or "DESC". Example: {"time": "DESC"} for most recent first. |
limit | number | — | Maximum number of records to return. Default: 10, Maximum: 100. Keep small for telemetry queries. |
query | object | — | Filter criteria for Kubernetes Cost Allocations. Always include a time-range filter. Each field accepts a direct value (exact match) or an operator object {"_ty |
select | object | — | Fields to return, as an object of field names to true (e.g. {"time": true, "body": true}). Select only the fields you need — telemetry rows can be large. |
Parameters from the server's own tool schema.
Why list_kubernetes_cost_allocations is rated Low
Even though list_kubernetes_cost_allocations only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsHigh parameter count (133 properties)
Attacks that exploit this kind of access
The rule that runs list_kubernetes_cost_allocations safely
PolicyLayer is an MCP gateway: it sits between your AI agents and OneUptime, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_kubernetes_cost_allocations, this is the rule to start with:
list_kubernetes_cost_allocations 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 OneUptime, apply this rule, and every list_kubernetes_cost_allocations call is checked against it from then on.
Questions about list_kubernetes_cost_allocations
Query Kubernetes Cost Allocations telemetry data from OneUptime. IMPORTANT: telemetry tables are large — always filter by a time range and keep limits small (e.g. 10-50). Each field accepts a direct value (exact match) or an operator object {"_type": "<Operator>", "value": ...}. Operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, GreaterThan, LessThan, GreaterThanOrEqual, LessThanOrEqual, InBetween (numbers/dates), Search (partial text), Includes (array of values). Example — items from the last 24 hours: {"createdAt": {"_type": "GreaterThan", "value": "2026-01-01T00:00:00.000Z"}}. It is categorised as a Read tool in the OneUptime MCP Server, which means it retrieves data without modifying state.
list_kubernetes_cost_allocations accepts 5 parameters: skip, sort, limit, query, select. The full parameter table on this page comes from the server's own tool schema.
Register the OneUptime MCP server in PolicyLayer and add a rule for list_kubernetes_cost_allocations: 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 OneUptime. Nothing to install.
list_kubernetes_cost_allocations 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 list_kubernetes_cost_allocations 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 list_kubernetes_cost_allocations. 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.
list_kubernetes_cost_allocations is provided by the OneUptime MCP server (https://oneuptime.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on OneUptime, and thousands of servers like it.
This server
Across the catalogue