get_usage

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

SERVERGankdat SOURCEhttps://gankdat.com/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/com-gankdat-gankdat/get-usage.md

WHAT IT DOES

What get_usage does on Gankdat

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.

RISK

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 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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_usage safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Gankdat, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_usage, this is the rule to start with:

get_usage Allowed

get_usage is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Gankdat, apply this rule, and every get_usage call is checked against it from then on.

FAQ

Questions about get_usage

What does the get_usage tool do? +

Plan, credits used/granted/remaining for the presented API key. Free to call. It is categorised as a Read tool in the Gankdat MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_usage? +

Register the Gankdat MCP server in PolicyLayer and add a rule for get_usage: 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 Gankdat. Nothing to install.

What risk level is get_usage? +

get_usage is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_usage? +

Yes. Add a rate_limit block to the get_usage 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.

How do I block get_usage completely? +

Set action: deny in the PolicyLayer policy for get_usage. 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.

What MCP server provides get_usage? +

get_usage is provided by the Gankdat MCP server (https://gankdat.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Gankdat, and thousands of servers like it.

This server

All 9 Gankdat tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →