get_usage_dashboard

Read your subscriber usage dashboard: active instances, chat and AI-call totals, plus the last 30 days by day and by agent. This is a usage measurement, not billing; it does not replace usage_summary

SERVERProAgentStore SOURCEhttps://mcp.proagentstore.online/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/io-github-proagentstore-platform/get-usage-dashboard.md

WHAT IT DOES

What get_usage_dashboard does on ProAgentStore

AI agents call get_usage_dashboard to retrieve information from ProAgentStore 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_dashboard is rated Low

Tool only retrieves usage metrics and analytics without modifying data or triggering external actions.

From the tool's definition Read your subscriber usage dashboard: active instances, chat totals

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_usage_dashboard safely

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

get_usage_dashboard Allowed

get_usage_dashboard 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_dashboard": {}
  }
}

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

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

FAQ

Questions about get_usage_dashboard

What does the get_usage_dashboard tool do? +

Read your subscriber usage dashboard: active instances, chat and AI-call totals, plus the last 30 days by day and by agent. This is a usage measurement, not billing; it does not replace usage_summary. It is categorised as a Read tool in the ProAgentStore MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_usage_dashboard? +

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

What risk level is get_usage_dashboard? +

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

Can I rate-limit get_usage_dashboard? +

Yes. Add a rate_limit block to the get_usage_dashboard 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_dashboard completely? +

Set action: deny in the PolicyLayer policy for get_usage_dashboard. 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_dashboard? +

get_usage_dashboard is provided by the ProAgentStore MCP server (https://mcp.proagentstore.online/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ProAgentStore, and thousands of servers like it.

This server

All 243 ProAgentStore 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 →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

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