corpus_list_scanners
Enumerate registered scanner types and their supported file extensions.
This record as markdown: /tools/io-github-dreamrec-livepilot/corpus-list-scanners.md
What corpus_list_scanners does on Livepilot
AI agents call corpus_list_scanners to retrieve information from Livepilot without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why corpus_list_scanners is rated Low
This tool performs a read-only enumeration of system scanner types and their properties. It has no side effects, makes no changes to state, executes no external operations, and poses minimal risk if misused by an AI agent—the worst outcome would be disclosure of scanner metadata that is likely already known or easily discoverable.
From the tool's definition Tool name contains 'list' and description states 'Enumerate registered scanner types' — a query operation that retrieves metadata about available scanners and their file extension support without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
The rule that runs corpus_list_scanners safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livepilot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For corpus_list_scanners, this is the rule to start with:
corpus_list_scanners is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Livepilot, apply this rule, and every corpus_list_scanners call is checked against it from then on.
Questions about corpus_list_scanners
Enumerate registered scanner types and their supported file extensions. It is categorised as a Read tool in the Livepilot MCP Server, which means it retrieves data without modifying state.
Register the Livepilot MCP server in PolicyLayer and add a rule for corpus_list_scanners: 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 Livepilot. Nothing to install.
corpus_list_scanners is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the corpus_list_scanners 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.
Set action: deny in the PolicyLayer policy for corpus_list_scanners. 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.
corpus_list_scanners is provided by the Livepilot MCP server (livepilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livepilot, and thousands of servers like it.
This server
Across the catalogue