Get recent log lines for an app, filtered to a level and bounded in size. Defaults are SMALL (50 lines, last 15 minutes, warn+) — broaden only if needed. Returns {text, truncated, suggestion}.
AI agents call fleet_logs_recent to retrieve information from Fleet without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a log retrieval tool that queries existing application logs without side effects. It filters and bounds results but does not create, modify, delete, or execute anything. The default conservative bounds (50 lines, 15 minutes, warn+) and explicit warning to 'broaden only if needed' further confirm it is a safe read-only operation.
From the tool's definition Tool 'fleet_logs_recent' retrieves log lines with filtering and size bounds. Description emphasizes "Get recent log lines" with no mention of modification, deletion, or execution capabilities. Returns read-only data: {text, truncated, suggestion}.
Documented attack patterns abuse exactly the kind of access fleet_logs_recent gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Fleet, and nothing reaches the server without passing your rules. This is the rule we recommend for fleet_logs_recent:
{
"version": "1",
"default": "deny",
"tools": {
"fleet_logs_recent": {}
}
}fleet_logs_recent is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get recent log lines for an app, filtered to a level and bounded in size. Defaults are SMALL (50 lines, last 15 minutes, warn+) — broaden only if needed. Returns {text, truncated, suggestion}. It is categorised as a Read tool in the Fleet MCP Server, which means it retrieves data without modifying state.
Register the Fleet MCP server in PolicyLayer and add a rule for fleet_logs_recent: 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 Fleet. Nothing to install.
fleet_logs_recent 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 fleet_logs_recent 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 fleet_logs_recent. 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.
fleet_logs_recent is provided by the Fleet MCP server (wrxck/fleet). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Fleet, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
39 Fleet tools catalogued and risk-classified — across an index of 43,000+ MCP servers.