{
  "id": 19958437,
  "title": "Read-only OAuth is one boundary. Your agent still needs others.",
  "url": "https://urgent.news/2026/11/14/read-only-oauth-is-one-boundary-your-agent-still-needs-others",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-14T09:51:15.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/xplormity/read-only-oauth-is-one-boundary-your-agent-still-needs-others-251l"
  },
  "original_language": "en",
  "account": "Read-only OAuth permits an agent to access specific data without modifying it. However, the agent's capabilities extend beyond read-only access based on its additional functionalities.\n\nThe SearchDock client, an open-source Google Search Console interface, demonstrates this concept. This walkthrough focuses on its implementation rather than any live experiment. The examples provided are hypothetical and do not involve real data or credentials.\n\nWhen connecting an agent, consider four key questions: what the OAuth grant authorizes, which operations the adapter implements, what other tools the host agent can invoke, and where the returned data and credentials end up. These questions address different boundaries and cannot be answered by only examining one.\n\nInspecting the scope, SearchDock requests read-only access to Webmasters data: https://www.googleapis.com/auth/webmasters.readonly. The consent flow uses secure methods, such as a loopback callback and PKCE challenge. The granted scope determines the operations the agent can perform. However, a read-only scope does not limit the agent to read-only actions.\n\nThe adapter's implemented operations list includes reading analytics, sitemaps, and inspecting Google's indexed version of a URL. Importantly, it does not include operations for indexing URLs, which contradicts the notion that read-only access automatically limits the agent's actions.\n\nThe host agent may also invoke additional tools beyond the ones implemented by the adapter. These tools have their own set of capabilities that should be considered when assessing the agent's overall permissions.\n\nThe data returned by the adapter and stored locally should be handled carefully. Although the OAuth grant prohibits modifications, data stored on the host system could potentially be accessed or misused by unauthorized parties. It is crucial to ensure proper data protection measures are in place.\n\nIn summary, while read-only OAuth provides a basic level of security, it does not encompass the full range of an agent's potential capabilities. Assessing the agent's overall access and behavior requires considering its scope, implemented operations, associated tools, and the handling of returned data.",
  "summary": "By Xplormity Collective A coding agent asks for Search Console data. You approve a read-only Google scope. Can it change your website? The answer depends on which tool it uses next. Read-only OAuth limits the Google operations authorized by that grant. It does not turn the entire agent session into a read-only environment. An agent that can also edit files, run a shell or send messages still has…",
  "key_points": [
    "Read-only OAuth allows data access without modification",
    "SearchDock client demonstrates read-only implementation",
    "Agent's capabilities extend beyond read-only actions"
  ],
  "editors_take": "Relying solely on read-only OAuth scopes creates a false sense of security because an agent's total influence depends on its implemented operations, additional tools, and local data handling.",
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}