
What Are MCP Primitives in Model Context Protocol
MCP primitives are the five core building blocks of the Model Context Protocol that define how AI agents connect to external tools and data sources.
Posts tagged AI-Assisted are created with support from artificial intelligence. I use AI tools to research, draft, and refine ideas—combining human insight with machine precision to deliver clear, informed, and creative content.

MCP primitives are the five core building blocks of the Model Context Protocol that define how AI agents connect to external tools and data sources.

A subagent is a separate AI agent instance with its own context window that handles a scoped task independently, acting as both a specialization tool and a context pressure valve.

AGENTS.md is a repository-level markdown file that gives AI coding agents the project context they need to write correct code from the very first session.

Progressive disclosure is a three-level loading strategy that feeds AI agents only the context they need at the moment, keeping sessions fast and token costs low.

Agent skills are reusable markdown files that teach AI coding tools how to perform repeated tasks consistently, replacing ad-hoc prompts with version-controlled procedures.

Blast radius is the total scope of damage a compromised or malfunctioning AI agent can cause before anything stops it, and limiting it is the most practical security strategy you have.

Tool poisoning is a stealth attack that embeds malicious instructions inside MCP tool descriptions, corrupting your AI agent before a single user command is typed.

Slopsquatting is a supply chain attack where adversaries register package names that AI coding tools hallucinate, turning a simple install command into a security breach.

The lethal trifecta describes the dangerous combination of private data access, untrusted content exposure, and outbound action capability that makes AI agents exploitable.

Workslop is AI-generated output that appears complete and professional but quietly transfers the real work to whoever reviews, maintains, or builds on top of it.

Verification debt builds when AI agents write code faster than your team can review it. Learn what it costs and how to keep it under control.

You have been working with an AI coding agent for about an hour. The session started great. But now the agent is re-reading files it already modified, asking questions you already answered, and generating code that contradicts its own earlier…

You asked an AI coding agent to add a user profile feature. It came back with clean code, passing tests, and a working UI. Everything looks great until you realize it created a brand new users table instead of using…

For over two decades, an Oracle APEX application has lived inside the database as metadata you could only realistically touch through the App Builder. The export was a giant f100.sql file — fine for deployment, nearly useless for code review, diffing, or…

You polish your resume, click "Submit," and then… silence. No rejection, no interview, nothing. Before you blame your experience, understand the software sitting between you and the recruiter: the Applicant Tracking System (ATS). More than 97% of Fortune 500 companies and…

You're about to apply for a job, and the posting asks for a "CV" but everything you've ever written is a resume. Or you're applying abroad, and suddenly the rules feel different. The resume vs CV confusion trips up job seekers constantly,…

You can be a brilliant engineer and still get rejected before a human ever reads your application. The reason is almost never your code — it's your resume. A great software engineer resume does one job: it convinces a recruiter and an…

Imagine photocopying a photocopy. The first copy looks fine. The tenth is blurry. The hundredth is an unreadable smudge. Model collapse — sometimes called recursive contamination — is the AI equivalent of that decay. When models are trained on data produced by other models,…