Agentfleet

Appearance

Resources & Tools ​

Resources ​

A resource is an MCP server the platform can call — an API surface with a base URL and a path (typically /mcp).

Registering a resource does more than store a URL:

  • Agentfleet registers the resource with the identity provider as an API resource and binds its audience. Every token issued for this resource is audience-restricted to it — a token minted for one resource cannot be replayed against another.
  • The platform's client is granted access so it can discover the resource's tools.

Lifecycle ​

Resources are Active, Inactive, or Deleted. Tools can only be imported from an active resource, and steps can only run against active resources.

Tools ​

A tool is a callable operation imported from a resource — its name, description, JSON parameter schema, and OAuth scope all come from the MCP server's own advertisement.

Importing ​

Use Import tools on a resource. Discovery is idempotent:

  • New tools are registered.
  • Already-registered tools have their schemas and scopes refreshed.

Re-import whenever the upstream server changes its tool surface.

Per-session tool filtering

MCP servers may filter tools/list per caller (policy-filtered listings). A missing tool after import usually means the importing session lacked the scope to see it — not that the tool doesn't exist. Import with a sufficiently privileged principal, then verify the expected tools are present.

Scopes drive least privilege ​

The tool's scope is not documentation — it is enforced. When a step runs, the token exchange requests only that step's tool scope. The identity provider intersects the request with what the user and the agent are each allowed, so a step can never widen its own access. If a tool imports without a scope (or with a wrong one), correct it on the tool before using it in a step.

Agentfleet — agent workflow orchestration.

© Advantage Team