get_usage_stats
Статистика використання акаунту: план, загальний % використання capacity цього місяця, розбивка по категоріях (system_activity, database_records, file_storage, ui_and_apps, users_access, communications) у %.
This record as markdown: /tools/com-quintadb-mcp/get-usage-stats.md
What get_usage_stats does on QuintaDB
AI agents call get_usage_stats to retrieve information from QuintaDB without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_usage_stats is rated Low
This tool queries and returns usage metrics about an account's subscription plan and resource consumption. It has no side effects, does not modify data, and presents read-only analytics. The lowest severity is appropriate since misuse would only expose usage information already accessible to account owners, with no destructive or operational consequences.
From the tool's definition get_usage_stats retrieves account usage statistics (plan, capacity usage percentage, category breakdown) with no modification capability. Description indicates only data retrieval: 'Статистика використання акаунту' (account usage statistics).
Attacks that exploit this kind of access
The rule that runs get_usage_stats safely
PolicyLayer is an MCP gateway: it sits between your AI agents and QuintaDB, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_usage_stats, this is the rule to start with:
get_usage_stats 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 QuintaDB, apply this rule, and every get_usage_stats call is checked against it from then on.
Questions about get_usage_stats
Статистика використання акаунту: план, загальний % використання capacity цього місяця, розбивка по категоріях (system_activity, database_records, file_storage, ui_and_apps, users_access, communications) у %. It is categorised as a Read tool in the QuintaDB MCP Server, which means it retrieves data without modifying state.
Register the QuintaDB MCP server in PolicyLayer and add a rule for get_usage_stats: 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 QuintaDB. Nothing to install.
get_usage_stats 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_usage_stats 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_usage_stats. 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_usage_stats is provided by the QuintaDB MCP server (https://quintadb.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on QuintaDB, and thousands of servers like it.
This server
Across the catalogue