get_events_count

Count events for a device over the past N hours (default 24).

SERVERAPI-Central SOURCEsecure-ssid/centralmcp

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/secure-ssid-centralmcp/get-events-count.md

WHAT IT DOES

What get_events_count does on API-Central

AI agents call get_events_count to retrieve information from API-Central 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_events_count is rated Low

This tool retrieves aggregate event data without modifying, deleting, or executing operations. It queries historical event information for monitoring purposes. The operation is informational only with no side effects on the network infrastructure or data stores.

From the tool's definition Tool performs a count operation on events ('Count events') with no modification or deletion indicated. The description specifies retrieval of event counts over a specified time window, which is a read-only query operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_events_count safely

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

get_events_count Allowed

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

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

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

FAQ

Questions about get_events_count

What does the get_events_count tool do? +

Count events for a device over the past N hours (default 24). It is categorised as a Read tool in the API-Central MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_events_count? +

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

What risk level is get_events_count? +

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

Can I rate-limit get_events_count? +

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

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

get_events_count is provided by the API-Central MCP server (secure-ssid/centralmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on API-Central, and thousands of servers like it.

This server

All 590 API-Central 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 →