corpus_status

THE RISK

Low Risk

Why corpus_status needs a policy

The verb 'Checks' combined with 'presence and metadata' describes a read-only inspection activity. No code execution, data modification, deletion, or financial operations are implied. The tool supports the migration assistant's informational role by querying the state of documentation assets, making it a straightforward Read category operation with low severity.

From the tool's definition Tool name 'corpus_status' and description 'Checks the presence and metadata of generated documentation artifacts' indicate a query/inspection operation that retrieves status information about documentation without modifying, executing operations, or affecting…

Documented attack patterns abuse exactly the kind of access corpus_status gives an agent:

POLICY

How to control corpus_status

PolicyLayer is an MCP gateway — it sits between your AI agents and HeroUI Migration MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for corpus_status:

policy.json

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

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

Create a free account and register HeroUI Migration MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More HeroUI Migration MCP tools

Write rewrite_file Apply heuristic migrations to code and return the rewritten source plus diagnostics. Write migrate_file_code Applies heuristic transformations to convert HeroUI v2 code to v3 patterns. Read analyze_file Analyze code and return detailed findings about legacy imports, components, props, hooks a Read analyze_legacy_imports Quick heuristic scanner for HeroUI/NextUI v2 imports and symbols. Read analyze_tailwind_config Checks tailwind.config.js for legacy HeroUI plugins and content paths. Read audit_tailwind Analyze a Tailwind configuration file for legacy HeroUI patterns. Read check_v3_compatibility Checks if a file content follows HeroUI v3 patterns (no NextUI, uses compound API). Read compare_component Show presence/status of a component between v2 and v3, with alias lookup.

All 18 HeroUI Migration MCP tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about corpus_status

What does the corpus_status tool do? +

Checks the presence and metadata of generated documentation artifacts. It is categorised as a Read tool in the HeroUI Migration MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on corpus_status? +

Register the HeroUI Migration 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 HeroUI Migration MCP. 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 HeroUI Migration MCP server (sctg-development/heroui-migration-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every HeroUI Migration MCP tool call.

Start from HeroUI Migration MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →