Agentic AI Feature Management
Processes Jira webhook tickets using AWS Bedrock's Claude 3 Haiku to extract structured feature management requests from natural language support ticket descriptions. Provides three core tools for checking feature status, enabling features, and disabling features across customer accounts. Features comprehensive security measures including prompt injection detection, input sanitization, rate limiting, and audit logging. Built with a modular architecture separating the Lambda handler, MCP server, and security components, supporting both mock and production modes with OAuth2 authentication for external API integration.
Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-28.
Scan details: Circle-IR · 2026-09-28 · Appeal
View full trust & usage report →Metadata
- Version
- 1.0.0
- Skill type
- atomic
- Execution layer
- mcp-remote
- Category
- cloud-infra
- Source
- PulseMCP
- Author type
- human
- Last scanned
- 2026-09-28
- Updated
- 2026-09-28
Use via MCP
Resolve Agentic AI Feature Management from your agent
Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.
One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.
claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp --scope user for --scope project to commit it to .mcp.json.