Get last month usage and cost summary.
AI agents call get_last_month_summary to retrieve information from Vultr MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and reports past usage and cost information. It performs a read-only query of billing data with no side effects, no code execution, no data modification, and no financial transactions. The blast radius is minimal—misuse would only expose historical cost visibility, not enable unauthorized changes or payments.
From the tool's definition Tool name 'get_last_month_summary' and description 'Get last month usage and cost summary' indicate a retrieval operation that queries historical billing/usage data without modifying or executing any actions.
Documented attack patterns abuse exactly the kind of access get_last_month_summary gives an agent:
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_last_month_summary:
{
"version": "1",
"default": "deny",
"tools": {
"get_last_month_summary": {}
}
}get_last_month_summary is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get last month usage and cost summary. It is categorised as a Read tool in the Vultr MCP MCP Server, which means it retrieves data without modifying state.
Register the Vultr MCP server in PolicyLayer and add a rule for get_last_month_summary: 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.
get_last_month_summary 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 get_last_month_summary 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 get_last_month_summary. 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.
get_last_month_summary 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.
Start from Vultr MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
284 Vultr MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.