Skip to main content

Securing agent tools and MCP servers

Spot confused-deputy and tool-poisoning risks in an agent's tools and MCP servers, and add allow-lists, scoped credentials, approval screens and logging so a bad tool or tool result cannot cause real harm.

Pro 1 · Quality engineerabout 3 hours5 sections

Quick answer

Tools give agents real power. A poisoned tool description, a hostile tool result or an over-broad token can turn the agent against its own user, so vet, pin, scope and gate every tool.

Why it matters

Agents now connect to email, code, payments and company data through tools and MCP servers, many written by strangers. One malicious server or one tool result with hidden instructions can make a trusted agent leak data or act for an attacker. Security teams review exactly this.

Sign up free to read the whole lesson

The rest of this lesson: 5 parts, video lessons, the best course, practice and a quick check. It is free, takes a few seconds and needs no card.

Accounts are for learners aged 18 and over. Under 18? The quick answer and the first part of every lesson stay open: browse lessons by topic.

On the roadmap: AI Security Engineer

SecurityPro 1: Quality engineerVideo lessonsTool poisoningConfused deputyModel Context ProtocolExcessive agencyLeast privilegeHuman in the loop

Track

Today's AI turns are used

Lessons, roadmaps, videos, practice cards and the code playground stay free with your account, with no limit.