Should an MCP server show different tools to different users?
Yes, if the difference follows per request authorization. The MCP spec lets tool lists vary by granted scopes but not by connection. Why that is safer.
Deep dives, practical guides, and incident analyses from engineers who build Safeguard. No fluff, no vendor FUD — just what you need to ship secure software.
Yes, if the difference follows per request authorization. The MCP spec lets tool lists vary by granted scopes but not by connection. Why that is safer.
Security for AI protects your models and agents; AI for security uses models to help analysts. Learn to tell them apart and ask the right buyer questions.
For developers using AI assistants, add review skills, dependency checks, secrets hygiene and policy to training. A syllabus with practice tasks.
AI coding assistants can suggest unfamiliar or nonexistent packages. What to ask and test when an SCA tool must cover AI-assisted development.
AI assistants change code volume and review habits. What to test in a static analysis evaluation: large diffs, pull request fit and secrets coverage.
AI assistants add packages fast, sometimes wrong ones. Ask a scanner vendor about checks at suggestion time, in the pull request and after merge.
A prompt that says never do X is a request, not a control. Which agent limits belong in code and policy, and which can safely stay in the prompt.
Policy cannot filter prompt injection away, so it limits what a hijacked agent can do: least privilege, approval for risky actions, untrusted input rules.
Sending prompts with personal data to an AI API raises residency and transfer questions. A ten point checklist of what to confirm before you ship.
Weekly insights on software supply chain security, delivered to your inbox.
Your first fix PR is minutes away.
No sales call required, even your agent can complete the purchase over MCP.