# Draw the coding agent's execution surface before granting autonomy

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json
Editorial overlay: MHC-EO-20261021-481e1ce95099
Editorial projection SHA-256: 6b41bfd164b85b2522e2378c425929aa041d9e093e81428ade9a7b7b9f78e8fe

---

## Draw the coding agent's execution surface before granting autonomy

ID: MHC-D-RESEARCH-0651 · Version: 0.1.0 · Kind: checklist
Source: https://vedokrok.com/knowledge/draw-the-coding-agent-s-execution-surface-before-granting-autonomy

The risk boundary is the set of things the agent can cause, not the chat window.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- A coding agent can edit code, run commands or call tools, but nobody has mapped what that actually reaches.

### Avoid when

- The map becomes stale when tools, workflows or agent products change; repeat it after material configuration changes.

### Explanation

List repository write access, shell commands, network egress, package installation, MCP/tools, CI triggers, secrets and deployment paths. Mark which actions are read-only, reversible, privileged or externally visible. Use the map to remove capability the task does not need.

### Checklist

- Repository write scope known.
- Shell/runtime capability known.
- Network path known.
- Tools/MCP known.
- Secrets and CI exposure known.
- Deployment or production path known.

### Example

A docs task reveals the agent also has package-install and workflow-write capability, so those permissions are removed for the task.

### Check

You can name the highest-impact action the agent could currently take and why it needs that access.

### Limits

- The map becomes stale when tools, workflows or agent products change; repeat it after material configuration changes.

### Evidence and sources

- supports: NIST SSDF recommends integrating secure development practices into the software lifecycle rather than treating security as a separate late-stage review. — RS-F8FE84C698B3B53A. The framework is high-level and must be tailored to the organization's development model and risk. (SSDF overview)
- supports: NIST SP 800-218A adds AI-specific practices and considerations to the existing SSDF, reinforcing that AI-enabled development inherits ordinary software-security obligations plus additional AI risks. — RS-26F11AEA8D93DB43. SP 800-218A targets producers and acquirers of AI models and systems broadly; coding-assistant controls here are a narrower adaptation. (Abstract and introduction)
- RS-F8FE84C698B3B53A: Secure Software Development Framework (SSDF) Version 1.1 — https://csrc.nist.gov/pubs/sp/800/218/final
- RS-26F11AEA8D93DB43: Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile — https://csrc.nist.gov/pubs/sp/800/218/a/final

### Vedokrok editorial review

Map what the coding agent can actually reach

A task can be small while the agent's access is large. Check the active environment before deciding how much work it may do on its own.

#### Map actions to resources

List what the agent can read, change, execute and send. Include files, shell commands, package installs, network calls, tool servers and CI or deployment jobs. For each route, record the resource, the identity used and the control that restricts access. Follow the whole route: a connected tool may reach a service that the local workspace cannot.

#### Check one unwanted route

For a documentation task, check whether the same environment can also modify a release workflow or reach a deployment service. Remove access the task does not need. Then use a safe permission check to confirm that the unwanted route is blocked. Update the map when tools or credentials change; a written inventory does not enforce a boundary.

**Editorial takeaway:** Keep a short record of each allowed action, its target and its enforcement point. If you cannot verify a high-impact route, resolve that gap before granting more autonomy.

#### Editorial evidence

- supports: OWASP treats coding-agent tools, runtime permissions and downstream automation as security boundaries requiring restricted access. — RS-1C68AE8325C384C0. Selected passages read on 2026-10-04. The compact inventory and safe permission probe are editorial adaptations, not an OWASP certification procedure. (Threat Model and Trust Boundaries; sections 4 MCP and Tool Security, 5 Agent Runtime Sandboxing, and 11 CI/CD Agents)
- contextualizes: NIST SSDF describes high-level secure development practices to integrate into a software development lifecycle. — RS-F8FE84C698B3B53A. Abstract read on 2026-10-04. It supplies lifecycle context, not direct evidence for every coding-agent runtime control. (Publication abstract, paragraphs 1–3)
- limits: NIST SP 800-218A covers AI model development and integration; deployment and operation of AI systems are outside its scope. — RS-26F11AEA8D93DB43. Selected PDF passages read on 2026-10-04. This limits the original broad application of the profile. Use coding-specific guidance for the operational checklist; no complete assessment is claimed. (SP 800-218A, section 1 Scope, printed page 2 (PDF page 10); section 2, printed page 4)
- RS-1C68AE8325C384C0: Secure Coding with AI Cheat Sheet — https://cheatsheetseries.owasp.org/cheatsheets/Secure_Coding_with_AI_Cheat_Sheet.html
- RS-F8FE84C698B3B53A: Secure Software Development Framework (SSDF) Version 1.1 — https://csrc.nist.gov/pubs/sp/800/218/final
- RS-26F11AEA8D93DB43: Secure Software Development Practices for Generative AI and Dual-Use Foundation Models: An SSDF Community Profile — https://csrc.nist.gov/pubs/sp/800/218/a/final

Editorial version: 1.0.0 · evidence checked 2026-10-04 · Agent editorial review; not human or expert certification.

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/give-the-agent-only-the-tools-this-job-needs
