lockdown: close #40, Chrome MCP write-action denies superseded by Playwright migration #62
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally filed by @coilysiren on 2026-05-02T01:10:09Z - https://github.com/coilysiren/coily/issues/41
Kai has disabled the Chrome MCP integrations on the machines running the daily routines, and the two routines that needed browser-driven scraping (daily-educational against CNCF Slack, daily-recruiting against LinkedIn) are migrating to Playwright with
playwright-extrastealth and per-servicestorageState.json. Tracked in coilysiren/coilyco-ai#91.That removes the entire write-path threat surface coilysiren/coily#40 was trying to harden via tool-level denies and a PreToolUse hook. With Chrome MCP gone from the agent's toolset on those hosts, denying its write-capable sub-tools no longer carries weight.
Action
If Chrome MCP comes back
If a future routine reintroduces Chrome MCP for genuine read-only use (one-off interactive work that Playwright is the wrong tool for), revisit the threat model from #40 at that point. The hook design in #40's body is still the right shape if it ever needs to be implemented, just not today.