agentsh-policy-create

Create AgentSH Policy

Overview

Create new AgentSH security policies from built-in templates, customized to the user's use case. Produces valid YAML policy files with correct structure, evaluation semantics, and defensive defaults for file, network, command, HTTP service, and Postgres-family database controls.

When to Use

• User asks to create/make/generate a new policy
• User describes a use case that needs a policy ("policy for my CI pipeline")
• User wants to set up AgentSH for the first time
• User wants controlled access to a declared HTTP API or Postgres-family database
• NOT for editing existing policies (use agentsh-policy-edit)

Flow

1. Locate policy directory

   • Look for config.yml or config.yaml in the project root to find policies.dir
   • If not found, look for a configs/policies/ directory
   • Fall back to asking the user with AskUserQuestion

2. Understand the use case Use AskUserQuestion to ask: "What will this policy protect?"

   Use Case	Template
   AI agent (code tasks)	default or agent-default
   CI/CD pipeline	ci-strict
   Local development	dev-safe
   Strict agent sandbox	agent-sandbox
   Observation/profiling	agent-observe
   Declared HTTP API gateway	Start from default
   Postgres-family database access	Start from default
   Custom / other	Start from default

3. Select template

   • Read the matching template from the policy directory (e.g., configs/policies/default.yaml)
   • On Windows, prefer the -windows variant if available (e.g., default-windows.yaml, ci-strict-windows.yaml)
   • If templates are not available locally, use the schema reference to generate a baseline

4. Customize Based on the template read in Step 3, ask only about gaps — skip categories the template already handles well:

   • "Which domains does your app need to reach?" → add network rules
   • "Any paths outside the workspace it needs?" → add file rules
   • "Any commands to block or require approval?" → add command rules
   • "Should any HTTP APIs be exposed through AgentSH?" → add http_services plus providers when credential substitution is needed
   • "Should any Postgres-family databases be mediated?" → add db_services, database_connection_rules, database_rules, and policies.db