Expose reading and publishing separately

An original publishing server could expose an article draft as a resource and a publish operation as a tool. Reading the draft should not implicitly publish it.

The host needs to preserve that distinction in both permissions and interface labels.

A protocol does not replace trust decisions

MCP does not make a connected service trustworthy by itself. Inspect what the server can expose and change, and apply your own authorization rules before using it.

Why the split exists

A resource has a URI and contents: a file, a row, a document. Reading it should not change the system.

A tool has a name and arguments and may change something: send, write, delete, pay. The protocol lets a client list both.

A careful client can show a person the tool list before a model is allowed to call one.

Servers sometimes put an action behind a resource because it was easier to implement. The client then “reads” a URI and a job starts.

That breaks the expectation a reviewer had. If the call has a side effect, make it a tool, with a description that says what changes.

If it is only data, make it a resource, and do not log it as a successful action.

What a client still has to enforce

MCP does not by itself grant permission. The host decides which servers are installed and which tools may run without a prompt.

A tool description is not a sandbox. The server process has whatever rights the operating system gave it.

Review that process the way you would review any local integration.

Names collide when several servers are connected. A tool called “search” from two servers is two tools.

Log the server identity with the call. And treat resource contents as untrusted text.

A document fetched over MCP can carry instructions, the same way a web page can. Reading it is not a reason to obey it.

What to record before you rely on it

Inventory each connected server, its tools, and its resources. Mark which tools can change data.

Confirm that a resource read does not. Re-read the list when you update a server, because a new tool can appear in an upgrade the user experiences as “the same connector.”

Keep the model id, the date, and the inputs you used beside that note, so a later change can be compared with the same test. When the result is a failure, store the artifact and change the design.

Do not relax the check until the model happens to pass. Name a person who owns that failure.

A note with no owner and no inputs cannot be repeated, and a pass with no date cannot be compared with the next model id.

Common questions

Is a resource safer than a tool?

Only if reading it truly has no side effect. Check the server.

A mislabeled resource is an action with a friendly name.

Does supporting MCP mean the agent is approved?

No. It means a client can speak the protocol. Approval is the host’s allow-list, the operating system’s permissions, and a person’s decision to run a tool.

Sources & further reading

  1. MCP: Architecture overview ↗
How this story was made

Written by Kristian Kostov with AI assistance and checked against the linked sources. Company performance claims are attributed to the company. Analysis reflects AiLookout’s interpretation; we have not independently tested the products discussed. Cover photography is illustrative and does not depict the specific announcement or product.

Our editorial standards
Back to all stories