{"version":"2.1.311","anchor":"remote-control-server-mount-named-as-a-policy-source","canonical_anchor":"remote-control-server-mount-named-as-a-policy-source","heading":"Remote Control server mounts are named as a policy source","tier":"internal","area":"Remote Control","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/remote-control-server-mount-named-as-a-policy-source","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Remote Control server mounts are named as a policy source\n\nClaude Code now uses the label Remote Control server mount when naming where a policy for a mounted MCP server came from\n\n**What**\n\nClaude Code now has a label, Remote Control server mount, for one source of policy. It is used for MCP servers that are mounted, meaning attached to the session from elsewhere. An MCP server is an add-on that gives Claude extra tools.\n\n**Why**\n\nWhere a policy applies to an MCP server mounted this way, Claude Code can say where it came from.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: both\n- Heads-up: no"}