Agentlock
- Olum289/agentlock
AgentLock is an MCP server that enforces policy, approval, and audited execution for AI agents without sharing secrets.
About
AgentLock is a hosted security gateway exposed as a remote MCP server so AI agents can run tools under policy, human approval, and audit trails instead of inheriting your secrets. developers shipping Claude Code or Cursor automations face a familiar trap: the agent needs API access, but pasting keys into prompts or config spreads risk fast. AgentLock sits in the middle—agents request actions, policies decide what is allowed, sensitive credentials stay on the gateway side, and executions leave an audit footprint you can review. The registry lists streamable HTTP at app.agentlock.net/api/mcp with a required Authorization Bearer token from the dashboard. Version 0.2.0 signals an early but purposeful product focused on agentic appsec rather than generic WAF rules. Use it when moving from local experiments to agents that touch billing, infra, or customer data. It complements manual code review by governing runtime behavior, not by replacing secure coding practices in your repo.
- Remote streamable-http MCP at app.agentlock.net with Bearer API token
- Security gateway: policy rules, approval flows, and audited agent execution
- Designed so agents do not receive shared secrets directly
- Version 0.2.0 from Olum289/agentlock on GitHub
- Hosted dashboard for creating AgentLock API credentials
Agentlock by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add --transport http agentlock https://app.agentlock.net/api/mcp --header "Authorization: Bearer YOUR_TOKEN"Add your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Transport | HTTP |
|---|---|
| Auth | Required |
| Repository | Olum289/agentlock ↗ |
What it does
Put a policy and approval gateway in front of agent tool execution so secrets stay vault-side and actions stay audited.
Who is it for?
Best when you're promoting agent workflows from prototype to production and need approval gates and audit logs without building a custom security proxy.
Skip if: Static code-only projects with no agent tool use, or teams that already operate a full enterprise PAM stack integrated with every MCP tool.
What you get
After connecting AgentLock, agent tool calls flow through governed, auditable execution with secrets kept out of the model context.
- Policy-governed agent tool execution path
- Approval and audit records for sensitive actions
- Reduced secret exposure in agent prompts and local config
By the numbers
- Server version 0.2.0
- 1 remote streamable-http endpoint at app.agentlock.net/api/mcp
- Bearer Authorization header required for MCP access
Recommended MCP Servers
1Claw VaultHSM-backed vault secrets for AI agents (JIT fetch) plus prompt-injection and threat scanning.2
1passwordMCP server for 1Password service accounts — tools and resources for vaults and credentials18
402sentinel McpAssess an x402 counterparty's risk BEFORE paying: allow/review/block, scored on-chain (Base).1
A2adependencyinspector McpRemote MCP for A2A dependency inspector MCP, structured receipts, audit logs, and reviewer-ready evi
A2a Governance Bridge McpA2A Governance Bridge MCP server.A2aidentitytoll McpRemote MCP for A2A caller identity, scope policy, verdict receipts, and audit history.How it compares
Hosted agent security gateway MCP, not a local lint skill or penetration-testing toolkit.
FAQ
Who is AgentLock for?
AgentLock is for developers deploying AI agents that invoke real tools and APIs who want policy, approvals, and audits without exposing secrets to the model.
When should I use AgentLock?
Use it in Ship when agents are about to touch production integrations and you need governed execution before or alongside launch.
How do I add AgentLock to my agent?
Create an API token in the AgentLock dashboard, add the remote MCP URL with Authorization Bearer header in your MCP client, then route sensitive tools through the gateway.