MCP tools are actions an AI assistant can take in other software, like opening a pull request, editing a ticket or sending a Slack message. Before you trust one, check seven things: who made it, how it signs in, whether it can write data, what it can see, whether it has limits, whether it logs calls and how many tools it adds.
This post explains MCP tools in plain English, the three kinds you're probably running and those seven questions in more detail. No code, no config files.
What an MCP tool is, in one paragraph
MCP (Model Context Protocol) is an open standard that lets AI apps connect to other software. An MCP server is a small program that plugs into your AI app. Each server offers tools, and a tool is a button the AI can press, with a label that says what it does: "create issue", "search messages", "run query". The AI reads the labels, decides which button helps, and presses it. That's the whole idea.
Interest is high, but real use is still early. Postman's 2025 State of the API report found 70% of developers know about MCP, but only 10% use it regularly. A lot of people are at the "installed a few servers" stage right now.
The three kinds of tools you're probably running
Most MCP tools fall into one of three groups. It helps to know which group each of yours is in.
- Read-only tools: They look things up and change nothing. Docs search, error lookups, reading a page. Low risk.
- Write tools: They create, change or delete things. Opening pull requests, editing tickets, sending messages, running database queries. This is where surprises come from.
- Tools that reach outside your machine: Browser automation, payments, anything that talks to the internet or to real customers. A mistake here isn't contained to your laptop.
One server often has tools in all three groups. A GitHub server can both read code and merge a pull request.
7 questions to ask before you trust an MCP server
You don't need to be a security engineer to vet an MCP server. You need these seven questions.
- Who made it? A server from the company behind the product (GitHub, Notion, Stripe) gets security fixes. A fork from an unknown account may not.
- How does it sign in? Signing in through your account (OAuth) is easier to revoke than a long-lived token pasted into a config file.
- Can it write? If yes, turn on approval before each write, or use a read-only mode if there is one.
- What can it see? Check the access it asks for. A tool that needs one project shouldn't see your whole organization.
- Is there a limit? Agents can get stuck in loops. A tool with no rate limit can make a lot of calls fast.
- Can you see what it did? If nothing is logged, you can't work out what happened after a mistake.
- How many tools does it add? Every tool's label takes up room in the AI's memory for that conversation. A server with 80 tools can make your assistant slower and more likely to press the wrong button.
One more thing worth knowing: the MCP specification itself tells AI apps to treat a tool's own description of its behavior as untrusted unless the server is trusted. A tool labeled "read-only" is a hint, not a promise. That's why question one matters most.
Six tools that pass the check for most people
These are all made by the company behind the product, and each has a clear job.
| Tool | What it does | Can it write? |
|---|---|---|
| GitHub MCP Server | Reads code, manages issues and pull requests | Yes. Use a narrow token. |
| Context7 | Pulls current library docs into your coding assistant | No |
| Playwright MCP | Drives a browser for testing | Yes, in the browser |
| Supabase MCP | Queries your database | Yes, but has a read-only mode |
| Sentry MCP | Looks up production errors | Mostly reads |
| Notion MCP | Searches and edits your workspace | Yes |
If you're starting from zero, Context7 and Sentry are the gentlest first installs. They mostly read, and they're useful on day one.
When it's your company's APIs, not a public server
Everything above is about public servers for public products. The questions change when you want an AI agent to use your company's own APIs: orders, billing, customer records.
Now you own the data, and someone in security will ask who approved the agent's access, which tools it can call and where the log is. Answering that for one agent is manageable. For ten agents across five teams, it usually means putting all the tools behind one gateway that handles access and logging in one place. DigitalAPI is one example of a platform that does that, turning existing APIs into MCP tools with permissions per agent.
I wrote a longer guide that covers how MCP tools work, ten worth trying and how to turn your own APIs into tools: What Are MCP Tools? 10 MCP Tools and Servers to Try in 2026.
Over to you
Open your MCP settings and count two things: how many servers are connected, and how many of them can write.
What were your two numbers?

