servers_count

Read servers.count through the Appaloft application operation catalog. Shared with CLI and HTTP/API.

SERVERAppaloft SOURCE@appaloft/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/appaloft-mcp/servers-count.md

WHAT IT DOES

What servers_count does on Appaloft

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

RISK

Why servers_count is rated Low

This tool retrieves server count information with no side effects, no data modification, and no external execution. It is a simple read/query operation. The explicit use of 'Read' in the description and the read-only nature of counting operations place this firmly in the Read category with low severity—misuse would only expose numeric metadata about servers.

From the tool's definition Tool description explicitly states 'Read servers.count' and the name 'servers_count' indicates a query operation that retrieves a count metric.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs servers_count safely

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

servers_count Allowed

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

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

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

FAQ

Questions about servers_count

What does the servers_count tool do? +

Read servers.count through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Read tool in the Appaloft MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on servers_count? +

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

What risk level is servers_count? +

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

Can I rate-limit servers_count? +

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

Set action: deny in the PolicyLayer policy for servers_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 servers_count? +

servers_count is provided by the Appaloft MCP server (@appaloft/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Appaloft, and thousands of servers like it.

This server

All 358 Appaloft tools →

Across the catalogue

The MCP Attack Database →

Guides

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