get_usage

THE RISK

Low Risk

Why get_usage needs a policy

This tool retrieves monitoring/observability data about database resource consumption. It performs a read-only query operation with no capability to modify, delete, or execute changes to infrastructure. The data returned is non-sensitive operational metrics used for visibility.

From the tool's definition Tool name 'get_usage' and description 'Get database usage statistics' indicate a retrieval operation that queries CPU, memory, and disk metrics without modification or side effects.

Documented attack patterns abuse exactly the kind of access get_usage gives an agent:

POLICY

How to control get_usage

PolicyLayer is an MCP gateway — it sits between your AI agents and Vultr MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_usage:

policy.json

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

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

Create a free account and register Vultr MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Vultr MCP tools

Destructive delete Delete a block storage volume. Destructive delete_bare_metal_server Delete a bare metal server. Destructive delete_cdn_ssl_certificate Remove SSL certificate from a CDN zone. Destructive delete_cdn_zone Delete a CDN zone. Destructive delete_collection delete_collection Destructive delete_connection_pool Delete a connection pool. Destructive delete_dns_domain Delete a DNS domain and ALL its associated records Destructive delete_dns_record Delete a specific DNS record

All 284 Vultr MCP tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_usage

What does the get_usage tool do? +

Get database usage statistics (CPU, memory, disk). It is categorised as a Read tool in the Vultr MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_usage? +

Register the Vultr 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 Vultr MCP. 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 Vultr MCP server (rsp2k/mcp-vultr). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Vultr MCP tool call.

Start from Vultr MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →