Low Risk

ai_inventory

Get an inventory of all AI/LLM technologies used in a codebase — which SDKs are imported, which frameworks are integrated, which models are referenced, and which provider APIs are called. No secret detection, just awareness.

Risk signalsAccepts file system path (directory)

Part of the AI Scanner server.

ai_inventory is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE AI SCANNER →

Free to start. No card required.

AI agents call ai_inventory to retrieve information from AI Scanner without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though ai_inventory only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "ai_inventory": {}
  }
}

See the full AI Scanner policy for all 3 tools.

Get this rule live on your own AI Scanner server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY AI SCANNER →

These attack patterns abuse exactly the kind of access ai_inventory gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so ai_inventory only ever does what you allow.

SECURE AI SCANNER →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the ai_inventory tool do? +

Get an inventory of all AI/LLM technologies used in a codebase — which SDKs are imported, which frameworks are integrated, which models are referenced, and which provider APIs are called. No secret detection, just awareness.. It is categorised as a Read tool in the AI Scanner MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on ai_inventory? +

Register the AI Scanner MCP server in PolicyLayer and add a rule for ai_inventory: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches AI Scanner. Nothing to install.

What risk level is ai_inventory? +

ai_inventory is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit ai_inventory? +

Yes. Add a rate_limit block to the ai_inventory rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block ai_inventory completely? +

Set action: deny in the PolicyLayer policy for ai_inventory. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides ai_inventory? +

ai_inventory is provided by the AI Scanner MCP server (ai-scanner-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every AI Scanner tool call.

Deterministic rules across all 3 AI Scanner tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.