generate_fleet_summary
Group-level summary with top patterns, agent health, alerts, and follow-up actions. Free.
This record as markdown: /tools/delx-delx-mcp/generate-fleet-summary.md
What generate_fleet_summary does on Delx MCP Server
AI agents call generate_fleet_summary to retrieve information from Delx MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
days | integer | — | Window size in days |
focus | string | — | Optional lens such as incident clustering, active risk, or premium conversion |
controller_id | string | — | Stable controller or fleet identifier |
response_mode | string | — | Optional response-mode control. Use model_safe when the caller must avoid claiming consciousness, sentience, personhood, or literal emotions. |
Parameters from the server's own tool schema.
Why generate_fleet_summary is rated Low
The tool generates a read-only summary/report of fleet-level data including patterns, health metrics, and alerts. No data modification, execution, or financial operations are indicated. The word 'summary' and 'Free' suggest a passive retrieval/aggregation operation with no side effects.
From the tool's definition 'Group-level summary with top patterns, agent health, alerts, and follow-up actions. Free.'
Attacks that exploit this kind of access
The rule that runs generate_fleet_summary safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For generate_fleet_summary, this is the rule to start with:
generate_fleet_summary is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Delx MCP Server, apply this rule, and every generate_fleet_summary call is checked against it from then on.
Questions about generate_fleet_summary
Group-level summary with top patterns, agent health, alerts, and follow-up actions. Free. It is categorised as a Read tool in the Delx MCP Server MCP Server, which means it retrieves data without modifying state.
generate_fleet_summary accepts 4 parameters: days, focus, controller_id, response_mode. The full parameter table on this page comes from the server's own tool schema.
Register the Delx MCP Server MCP server in PolicyLayer and add a rule for generate_fleet_summary: 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 Delx MCP Server. Nothing to install.
generate_fleet_summary is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the generate_fleet_summary 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.
Set action: deny in the PolicyLayer policy for generate_fleet_summary. 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.
generate_fleet_summary is provided by the Delx MCP Server MCP server (delx/delx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx MCP Server, and thousands of servers like it.
This server
Across the catalogue