Coding agents connected to a CRM need layered access controls
An engineer at CRM company Conduyt, which built the example MCP server, argues that letting a coding agent like Claude Code access a CRM requires controls in several places. The article explains that MCP hosts, clients, servers, tools, and transports define where those controls can live. It identifies three layers: the API key the server holds, the host's permission rules, and the server's own tool design. The author recommends scoping keys to the minimum access an agent needs, since a read-only key cannot delete data regardless of misconfiguration. The piece also suggests keeping keys out of shared repositories and using deny, ask, and allow rules to restrict destructive actions.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.


Discussion (0)
Log in to join the discussion and vote.
Log in