Skip to main content

Scanner

AI SecOps - query security data lakes, execute investigations, and fetch query results

Tools

3 available tools

Search the tool definitions captured from the MCP server. The live list can vary with version, deployment, and credentials.

3 tools found.

  • Get Scanner context

    Read only

    Tool name: get_scanner_context

    Get context about available Scanner indexes and data sources for investigation

  • Execute query

    Read only

    Tool name: execute_query

    Execute a search query against Scanner security data lake indexes

  • Fetch query results

    Read only

    Tool name: fetch_query_results

    Fetch results from a previously executed Scanner query

Compatibility

Connect Scanner to the clients your teams already use

19 AI clients can connect to Scanner through Runlayer. Pick one for its setup steps and controls.

Why Runlayer

Why connect Scanner through Runlayer?

One approved path

Approve Scanner once and everyone gets it in the AI clients they already use. Runlayer holds the credentials, so nothing sits in client configuration.

Fine-grained policy

Control who can use each server, tool, and resource, and under which runtime conditions.

Runtime security

Scan tool inputs and outputs for prompt injection, credential exposure, PII, and data exfiltration, then alert, mask, or block.

Audit and observability

Trace every request across users, clients, tools, policies, scanner decisions, and downstream systems.

Frequently asked questions