fleet_agent_capabilities
Estado de configuración de un FleetAgent (lo mismo que GET /api/v2/fleet-agents/:id/capabilities): conectores (
This record as markdown: /tools/cloud-easybits-easybits/fleet-agent-capabilities.md
What fleet_agent_capabilities does on EasyBits
AI agents call fleet_agent_capabilities to retrieve information from EasyBits without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why fleet_agent_capabilities is rated Low
Retrieves FleetAgent configuration state and capabilities; read-only query with no side effects.
From the tool's definition Estado de configuración, GET /api/v2/fleet-agents/:id/capabilities
Attacks that exploit this kind of access
The rule that runs fleet_agent_capabilities safely
PolicyLayer is an MCP gateway: it sits between your AI agents and EasyBits, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fleet_agent_capabilities, this is the rule to start with:
fleet_agent_capabilities 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 EasyBits, apply this rule, and every fleet_agent_capabilities call is checked against it from then on.
Questions about fleet_agent_capabilities
Estado de configuración de un FleetAgent (lo mismo que GET /api/v2/fleet-agents/:id/capabilities): conectores (. It is categorised as a Read tool in the EasyBits MCP Server, which means it retrieves data without modifying state.
Register the EasyBits MCP server in PolicyLayer and add a rule for fleet_agent_capabilities: 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 EasyBits. Nothing to install.
fleet_agent_capabilities 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_agent_capabilities 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_agent_capabilities. 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_agent_capabilities is provided by the EasyBits MCP server (@easybits.cloud/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on EasyBits, and thousands of servers like it.
This server
Across the catalogue