Table of contents

Add secure integrations to your products and AI agents with ease via Merge.
Get a demo

The hidden security threats of MCP—and how to mitigate them

Gil Feig
CTO and co-founder
at Merge

The Model Context Protocol (MCP) offers an incredibly powerful way to integrate your LLM with outside data sources, but you’ll need to take certain security measures when using it.

Otherwise, you risk leaking sensitive information on your business, your customers’ businesses, and—if you’re implementing customer-facing integrations—your end users.

Here are some of the biggest security threats to consider and how you can address them.

{{this-blog-only-cta}}

Prompt injection threats

If your customers use API keys to authenticate with your MCP server, they’re trusting you—the MCP provider—to keep these credentials safely stored and away from malicious actors.

Unfortunately, you can easily break their trust.

Researchers at Cornell found that Malicious actors can find ways to use inputs—such as a document with instructions—that coerce you LLM to provide authentication credentials. 

This isn't a hypothetical scenario. We're now seeing catastrophic incidents come up. Case in point: attackers recently exploited a prompt injection vulnerability on GitHub’s MCP server to access private repository data.

Related: Why MCP servers are difficult to use

Comprehensive API scopes 

Since MCP is so flexible, you’ll likely want to expose as many tools (which correspond to API endpoints) as possible. 

This’ll lead you to support keys that access a wide range of sensitive data across applications, whether that's social security numbers, business financials, customers’ payment information, and so on.

This will only up the stakes of a key interception.

A single point of failure

MCP servers might store API keys in a single place. This gives an attacker a single target to access API keys that—as our previous section touched on—support multiple services. 

For instance, if you’re using MCP to support internal integrations, you now have a single service that exposes data and functionality for multiple services, like a CRM (e.g., Salesforce), a marketing automation platform (e.g., HubSpot), and a ticketing solution (e.g., Zendesk). This means that if the agent or server is successfully attacked, data from all of the applications can be exposed. 

Why MCP server is a single point of failure

Scenarios like these would be extremely difficult to address, and even if they are, they’d cause long-term damage to your company’s reputation both internally and externally. 

https://www.merge.dev/blog/mcp-best-practices?blog-related=image

Poorly-documented tools

If your MCP server’s tools aren’t descriptive or use names that don’t accurately describe their functions, your LLM can easily choose the wrong tool from a given input and potentially invoke a tool that reveals sensitive information.

For instance, if a user wants to get an update on a ticket related to onboarding a specific customer from their project management system, the LLM can mistakenly share another ticket that includes information on a new hire—such as sensitive details from the new hire’s collected documents.

https://www.merge.dev/blog/api-vs-mcp?blog-related=image

How to address these security threats

When you put all of this together, the security threats associated with MCP only grow in severity and likelihood.

For example, if an MCP server stores a few comprehensive API keys in a single place, a significant amount of sensitive information is more vulnerable to exposure. And if you consider the different attack vectors—from prompt injections to indirect access via unsecure connections—your chances of getting breached will be higher. 

Fortunately, you can use Merge Agent Handler—a single platform to securely connect your AI agents to thousands of tools—to avoid these security issues altogether. 

Overview on Merge Agent Handler
Overview on Merge Agent Handler

It can support your agents’ security needs by providing: 

  • Per-identity authentication at call time and least‑privilege boundaries on the connectors and tools an agent can use (via Tool Packs)
  • Fully maintained MCP servers for a variety of 3rd-party applications
  • Optimal tool names and tool descriptions
  • Robust integration observability features (e.g., fully-searchable logs and customizable alerts) to help you detect and address potential security threats
  • An Evaluation Suite that lets you test any tool and connector 

Start using Merge Agent Handler today by signing up for a free account!

Gil Feig
CTO and co-founder
@Merge

Read more

8 best practices for building secure and reliable AI agents

AI

Model Context Protocol (MCP) tools: what you need to know

AI

MCP connectors: how they work and real-world examples

AI

Subscribe to the Merge Blog

Get stories from Merge straight to your inbox

Subscribe

Ready to integrate your AI agents with enterprise-grade tools?

Merge Agent Handler lets you securely connect your AI agents to thousands of tools and monitor and manage every tool call. Learn more

Learn more
But Merge isn’t just a Unified 
API product. Merge is an integration platform to also manage customer integrations.  gradient text
But Merge isn’t just a Unified 
API product. Merge is an integration platform to also manage customer integrations.  gradient text
But Merge isn’t just a Unified 
API product. Merge is an integration platform to also manage customer integrations.  gradient text
But Merge isn’t just a Unified 
API product. Merge is an integration platform to also manage customer integrations.  gradient text