metadata_recompute_baseline

THE RISK

Critical Risk

Why metadata_recompute_baseline needs a policy

The tool explicitly erases existing metadata (irreversible deletion) before re-indexing. The erasure of metadata cannot be undone, making this a Destructive action. The blast radius is high because erasing and recomputing the baseline index for an entire codebase could disrupt duplicate detection, lose suppression history, and require significant reprocessing time.

From the tool's definition Erase metadata and re-index the codebase from scratch

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

POLICY

How to control metadata_recompute_baseline

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

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "metadata_recompute_baseline"
  ]
}

metadata_recompute_baseline disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

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

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Astrograph tools

Destructive metadata_erase Erase all persisted metadata. Resets server to idle. Write edit Edit file. Blocks if new code duplicates existing, warns on similarity. Write generate_ignore Auto-generate .astrographignore with reasonable defaults for excluding files from indexing Write lsp_setup Inspect and configure deterministic LSP command bindings Write set_workspace Set or change the workspace directory. Re-indexes the codebase at the new path. Write suppress Suppress a duplicate by WL hash (from analyze output). Only suppress AFTER confirming the Write unsuppress Unsuppress a hash. Write write Write file. Blocks if duplicate exists, warns on similarity.

All 12 Astrograph tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Astrograph → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about metadata_recompute_baseline

What does the metadata_recompute_baseline tool do? +

Erase metadata and re-index the codebase from scratch. It is categorised as a Destructive tool in the Astrograph MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on metadata_recompute_baseline? +

Register the Astrograph MCP server in PolicyLayer and add a rule for metadata_recompute_baseline: 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 Astrograph. Nothing to install.

What risk level is metadata_recompute_baseline? +

metadata_recompute_baseline is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit metadata_recompute_baseline? +

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

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

metadata_recompute_baseline is provided by the Astrograph MCP server (thaylo/astrograph). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Astrograph tool call.

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

CHECK YOUR STACK →