fleet_ping

Lightweight liveness check — returns server health status instantly without dispatching to fleet-manager. Use this to verify the MCP server is responsive before calling fleet_dispatch.

SERVERAgent Store SOURCEchrisluersen/agent-store

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/agent-store/fleet-ping.md

WHAT IT DOES

What fleet_ping does on Agent Store

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

RISK

Why fleet_ping is rated Low

fleet_ping performs a liveness check that retrieves health status information without modifying, executing, or affecting any system state. It is a simple diagnostic probe analogous to ICMP ping or HTTP health checks, making it a Read category tool with minimal risk.

From the tool's definition Tool description states it 'returns server health status instantly' and is used to 'verify the MCP server is responsive' — these are read-only diagnostic queries with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs fleet_ping safely

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

fleet_ping Allowed

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

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

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

FAQ

Questions about fleet_ping

What does the fleet_ping tool do? +

Lightweight liveness check — returns server health status instantly without dispatching to fleet-manager. Use this to verify the MCP server is responsive before calling fleet_dispatch. It is categorised as a Read tool in the Agent Store MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on fleet_ping? +

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

What risk level is fleet_ping? +

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

Can I rate-limit fleet_ping? +

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

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

fleet_ping is provided by the Agent Store MCP server (chrisluersen/agent-store). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Agent Store, and thousands of servers like it.

This server

All 19 Agent Store tools →

Across the catalogue

The MCP Attack Database →

Guides

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