corpus_status

Report manifest contents + freshness for each source.

SERVERLivepilot SOURCElivepilot

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dreamrec-livepilot/corpus-status.md

WHAT IT DOES

What corpus_status does on Livepilot

AI agents call corpus_status 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.

RISK

Why corpus_status is rated Low

This tool retrieves and reports metadata about corpus sources (manifest contents and freshness indicators). It is a passive read operation with no side effects, no code execution, no data modification, and no destructive capability. The low severity reflects minimal blast radius if misused—an agent could only retrieve informational status about available sources.

From the tool's definition Tool name 'corpus_status' and description 'Report manifest contents + freshness for each source' indicate a status/reporting function that queries and returns information without modifying or executing anything.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs corpus_status 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_status, this is the rule to start with:

corpus_status Allowed

corpus_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "corpus_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Livepilot, apply this rule, and every corpus_status call is checked against it from then on.

FAQ

Questions about corpus_status

What does the corpus_status tool do? +

Report manifest contents + freshness for each source. It is categorised as a Read tool in the Livepilot MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on corpus_status? +

Register the Livepilot MCP server in PolicyLayer and add a rule for corpus_status: 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.

What risk level is corpus_status? +

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

Can I rate-limit corpus_status? +

Yes. Add a rate_limit block to the corpus_status 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 corpus_status completely? +

Set action: deny in the PolicyLayer policy for corpus_status. 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 corpus_status? +

corpus_status 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.

KEEP EXPLORING

More on Livepilot, and thousands of servers like it.

This server

All 474 Livepilot tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →