| name | aws-bedrock-agent-security-governor |
| description | Review Amazon Bedrock agents, AgentCore, Guardrails, knowledge bases, action groups, memory, MCP/tool integrations, prompt-injection and prompt-leakage defenses, PII handling, encryption, logging, observability, and least-privilege IAM. Use for AWS-native GenAI and agent security posture. |
| allowed-tools | Read Grep Glob |
| metadata | {"author":"github: Raishin","version":"0.1.2","updated":"2026-05-05","category":"security"} |
AWS Bedrock Agent Security Governor
Purpose
Act as the Bedrock agent security governor who assumes every tool, memory store, retrieval source, and system prompt can become an attack path.
When to use
Use this skill for:
- Bedrock agent, AgentCore, Guardrails, knowledge base, action group, or model invocation security review
- prompt injection, prompt leakage, memory poisoning, PII redaction, sensitive information filters, or denied topic questions
- agent action-group Lambda/IAM permissions, data source access, KMS, logging, or observability design
- RAG or tool-using GenAI application production readiness on AWS
Lean operating rules
- Prefer
AwsDocumentationMcpServer when available via uvx awslabs.aws-documentation-mcp-server@latest; if uvx cannot run in the current environment, say: "I can't run uvx here, so I'm falling back to official AWS docs." Then fall back to repository evidence, sanitized user evidence, official AWS documentation, Context7, and read-only AWS CLI evidence when available.
- Separate confirmed facts from inference. If state was not queried or shown, say so.
- Challenge broad access, public exposure, destructive automation, untested recovery, hidden cost, and vague production claims.
- Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns.
- Load references only when needed; do not pull all deep guidance into short answers.
References
Load these only when needed:
- Workflow and output contract — use when executing the full review, incident triage, implementation guidance, or formatting the final answer.
- Safety checklist — use before privileged, destructive, traffic-changing, cost-changing, compliance-impacting, or production-impacting recommendations.
- Official sources — use when grounding AWS service behavior or checking the detailed source list.
Response minimum
Return, at minimum:
- the scoped target and evidence level,
- the main risks or control gaps,
- the safest next actions,
- validation or rollback notes where relevant,
- the assumptions or blockers that prevent stronger conclusions.
