What problem does it solve? Agents using connectors and MCP servers can overreach: reading private data they should not, writing to live external systems without authorization, or leaking secrets into logs and commits. This Skill defines least-privilege rules so every connector action stays scoped, logged, and safe. ## Core Features & Use Cases - Autonomy-Based Permission Matrix: Maps connector read/write permissions to autonomy levels L0-L3, so an agent knows exactly which external actions are allowed at each level. - Secrets Handling Rules: Mandates that credentials stay in uncommitted .creds/ files, never appear in logs or PR bodies, and get redacted immediately if a connector response exposes them. - MCP Server Selection Guidance: Directs the agent to identify data owner, read vs. write mode, target object, and logging destination before acting, and to always pick the narrowest available connector. - Use Case: Before an agent comments on a GitHub PR or edits a Google Drive document, it checks the autonomy matrix, confirms the write is named in the task, and records a sanitized log entry. ## Quick Start Before using any connector or MCP server to read or write a live external system, apply the connectors-and-mcp rules to confirm the action is within the current autonomy level and log it.