zernio_get_usage_stats

Get usage statistics for the workspace: posts published, messages sent, contacts, etc.

SERVERZernio SOURCEeyalm321/zernio-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/eyalm321-zernio-mcp/zernio-get-usage-stats.md

WHAT IT DOES

What zernio_get_usage_stats does on Zernio

AI agents call zernio_get_usage_stats to retrieve information from Zernio without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why zernio_get_usage_stats is rated Low

This tool retrieves and queries workspace usage metrics. It performs no write, delete, execute, or financial operations. The verb 'Get' and the informational nature of usage statistics (read-only analytics data) clearly place this in the Read category. Severity is low because accessing usage statistics poses minimal risk even if misused by an agent.

From the tool's definition Tool name 'zernio_get_usage_stats' and description 'Get usage statistics for the workspace: posts published, messages sent, contacts, etc.' indicate a retrieval operation with no data modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs zernio_get_usage_stats safely

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

zernio_get_usage_stats Allowed

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

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

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

FAQ

Questions about zernio_get_usage_stats

What does the zernio_get_usage_stats tool do? +

Get usage statistics for the workspace: posts published, messages sent, contacts, etc. It is categorised as a Read tool in the Zernio MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on zernio_get_usage_stats? +

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

What risk level is zernio_get_usage_stats? +

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

Can I rate-limit zernio_get_usage_stats? +

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

How do I block zernio_get_usage_stats completely? +

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

What MCP server provides zernio_get_usage_stats? +

zernio_get_usage_stats is provided by the Zernio MCP server (eyalm321/zernio-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Zernio, and thousands of servers like it.

This server

All 274 Zernio tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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