# get_usage

Plan, credits used/granted/remaining for the presented API key. Free to call.

Agent View of the PolicyLayer registry record for `get_usage`. HTML page: https://policylayer.com/tools/com-gankdat-gankdat/get-usage

## Facts

- Tool: `get_usage`
- Server: Gankdat (`https://gankdat.com/mcp`) — https://policylayer.com/tools/com-gankdat-gankdat.md
- Homepage: https://github.com/https://gankdat.com/mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_usage",
    "arguments": {}
  }
}
```

## Why get_usage is rated Low

This tool retrieves read-only account information (credits and usage data). It has no side effects, cannot modify data, and poses minimal security risk. Even if misused by an AI agent, it only exposes non-sensitive billing metrics specific to the API key holder.

From the tool's own definition: "Tool name 'get_usage' and description 'Plan, credits used/granted/remaining for the presented API key' indicates querying account/billing metadata. No modification, deletion, execution, or financial transaction occurs—only retrieval of usage statistics."

## Use case

AI agents call get_usage to retrieve information from Gankdat without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Gankdat:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_usage": {}
  }
}
```

## Other tools on Gankdat (8)

- `list_sources` — Read — https://policylayer.com/tools/com-gankdat-gankdat/list-sources.md
- `query_eu_ted` — Read — https://policylayer.com/tools/com-gankdat-gankdat/query-eu-ted.md
- `query_sam_exclusions` — Read — https://policylayer.com/tools/com-gankdat-gankdat/query-sam-exclusions.md
- `query_uk_companies` — Read — https://policylayer.com/tools/com-gankdat-gankdat/query-uk-companies.md
- `query_uk_insolvency` — Read — https://policylayer.com/tools/com-gankdat-gankdat/query-uk-insolvency.md
- `query_uk_planning` — Read — https://policylayer.com/tools/com-gankdat-gankdat/query-uk-planning.md
- `query_uk_sanctions` — Read — https://policylayer.com/tools/com-gankdat-gankdat/query-uk-sanctions.md
- `query_uk_tenders` — Read — https://policylayer.com/tools/com-gankdat-gankdat/query-uk-tenders.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-gankdat-gankdat · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-gankdat-gankdat