Techzine — DeepKeep AI Agent Scanner

AI relevance: The scanner targets agentic AI deployments, mapping tool access and data exposure to reduce prompt-injection and tool-abuse risk in production agent systems.

  • DeepKeep released a free AI Agent Scanner that inventories agent tool access, data sources, and vulnerabilities.
  • The scanner generates a visual risk map of connected tools, intents, and data paths across an agent deployment.
  • Risk mapping is aligned to the OWASP Top 10 for Agentic Applications, covering prompt injection, tool misuse, and supply-chain risks.
  • Supported ecosystems include Microsoft-based agent frameworks, Agentforce, OpenAI Agents, CrewAI, Amazon Bedrock AgentCore, n8n, and Make.
  • DeepKeep positions the scanner as a fast way to baseline where agents have sensitive access before broader rollout.
  • The company says runtime protection and red-teaming capabilities are planned as follow-on defenses.

Security impact

Agent scanners like DeepKeep make it clear how easy it is to find exposed tool endpoints, missing auth, or weak policies in AI deployments. For defenders, that’s a gift — but it’s also a warning: attackers can use the same visibility. AI stacks are often assembled quickly, and “temporary” agent endpoints routinely end up on public networks. That creates a wide, low‑friction attack surface.

The bigger risk is operational drift. Even if you harden today’s endpoints, new tools get added constantly. Without automated checks, exposed or misconfigured agents can persist for weeks. This is exactly the kind of latent exposure Adversaries exploit: low‑hanging fruit that no one is watching.

Mitigation strategy

Integrate agent scanning into CI/CD and asset inventory. Treat MCP servers, tool APIs, and agent gateways as first‑class assets with required auth and logging. Enforce least‑privilege networking by default and require security review for any new tool that accepts external input.

Why it matters

  • Agent deployments often sprawl across tools and data sources; visibility is the first control before enforcement.
  • Mapping tool access helps teams prioritize guardrails for the highest-risk integrations (e.g., secrets, ticketing, CI/CD).
  • Aligning to OWASP’s agentic risks provides a shared framework for audits and third-party assessments.

What to do

  • Baseline access: inventory which agents can reach sensitive systems and data stores.
  • Constrain tools: tighten permissions for high-risk tools and add allowlists for agent actions.
  • Monitor behaviors: add logging for tool calls and data egress to catch prompt-injection abuse early.
  • Track OWASP gaps: map your controls to the OWASP Top 10 for Agentic Applications to close coverage holes.

Sources