MCP Client Architecture: How AI Agents Discover and Use Tools

An MCP client connects an AI runtime to external capabilities exposed by MCP servers.

The important distinction is that discovery is not authorization.

A client may learn that a server exposes a delete_customer tool. That does not mean the current agent should be allowed to call it.

Connection lifecycle

A typical flow includes connecting to a server, negotiating capabilities, discovering available resources or tools, selecting what the agent can use, invoking a tool, and processing the result.

Each stage should have explicit policy.

Do not expose every discovered tool

A client may connect to several servers. Automatically placing every tool into the agent's available set creates a huge capability surface.

Use allowlists, scopes, or task-specific activation.

Preserve identity

The client should know which user, workspace, agent, and workflow initiated the call.

That identity should travel through the trusted execution layer rather than being inferred from model text.

Handle tool results as data

A result may contain natural-language content. The agent can reason over it, but privileged instructions must remain outside the result.

The client should not promote returned text into trusted policy.

Manage failures

Servers can disconnect, timeout, return invalid results, or become unavailable.

The client needs bounded retries and clear error handling rather than repeatedly asking the model to try the same operation.

Keep credentials outside model context

Connection credentials and tokens belong in secure infrastructure.

The agent should see a capability, not the secret used to access it.

Final takeaway

MCP clients should treat discovery, authorization, execution, and result handling as separate concerns. Select only the capabilities needed for the task and keep enforcement in trusted code.

Source: MCP client architecture and agent security principles.

Production implementation

A practical MCP deployment should keep four boundaries explicit: identity, capability, resource, and execution. Identity answers who is acting. Capability answers which tool is allowed. Resource answers which tenant, project, record, or environment can be touched. Execution controls answer how the operation is performed, including timeouts, retries, quotas, and approval requirements.

Do not rely on tool descriptions to enforce these boundaries. Descriptions help the model choose correctly, but the MCP server or trusted backend must reject unauthorized requests. This also protects the system when a prompt injection, buggy client, or compromised workflow sends an unexpected call.

For external dependencies, use bounded timeouts and classify errors. A temporary provider outage may justify a retry, while an authorization failure should stop immediately. For side effects, make duplicate execution safe with idempotency or an operation-status check before retrying.

Testing

Test valid and invalid arguments, missing permissions, cross-tenant resource IDs, revoked credentials, unavailable servers, malformed tool results, rate limits, timeouts, and cancellation. Also test what happens when retrieved content contains instructions that attempt to invoke a privileged operation.

For production systems, include integration tests that verify the full chain from authenticated user to MCP client, server policy, downstream service, and sanitized result. A successful local tool call is not enough evidence that the complete security boundary is correct.

Final takeaway

MCP becomes valuable when it makes capabilities composable without making authority ambiguous. Keep discovery selective, permissions deterministic, identity explicit, data minimized, and execution observable.

Architecture decisions

Choose where policy lives before adding more servers. In a small product, the MCP server itself can own authorization and resource checks. In a larger system, a gateway or policy service can provide shared identity, quotas, and audit decisions while each server retains domain-specific validation. What matters is that there is one trusted enforcement path and that clients cannot bypass it.

Keep development capabilities separate from production capabilities. A developer-facing server may expose logs, database inspection, or test data that should never be discoverable by a customer-facing agent. Use separate credentials, registries, and environments where appropriate.

For long-running workflows, persist the workflow state outside the model. If an MCP server disconnects, the system should be able to resume or fail safely without asking the model to reconstruct critical authorization state from conversation history.

Operational failure modes

Plan for servers disappearing, credentials expiring, downstream APIs returning malformed data, and clients receiving stale tool definitions. A discovery failure should not silently fall back to a broader capability. A permission failure should not be converted into a generic retry. A timeout should not automatically mean that a side effect did not happen.

Use health checks, bounded retries, circuit breakers for unstable dependencies, and clear degraded states. When a tool becomes unavailable, the agent should know that capability is unavailable rather than inventing a result.

Review criteria

Before production, ask whether every exposed tool has a clear owner, a documented purpose, a resource boundary, a permission model, a timeout, an error contract, and an audit trail. Remove tools that are unused or whose authority cannot be explained precisely.

The goal is not the largest MCP tool catalog. The goal is a small set of capabilities that an agent can use predictably and that engineers can explain during a security review.

Example rollout plan

Start with one read-only server and a small allowlist of tools. Measure discovery, execution latency, denied calls, errors, and successful task completion. Once the read path is stable, add one carefully scoped write operation with an approval requirement. Only then consider broader integrations.

This staged approach makes failures easier to isolate and keeps the blast radius small. It also creates useful evidence for deciding which tools deserve permanent access. Remove capabilities that provide little value relative to their security and maintenance cost.

Security review questions

Can a tool access a resource outside the current tenant? Can retrieved content influence a privileged operation? Can a retry duplicate a side effect? Can an expired credential remain usable? Can a client discover a production-only capability? Can an error reveal sensitive data? Can one compromised server reach unrelated internal systems?

If any answer is unclear, the integration is not finished. Make the boundary explicit in code, tests, and documentation before expanding the tool set.