sources_remove

Remove files from the open project without deleting them from disk.

SERVERAdr Fpga Bootstrap SOURCEzxyyz/adr-fpga-bootstrap

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/adr-fpga-bootstrap/sources-remove.md

WHAT IT DOES

What sources_remove does on Adr Fpga Bootstrap

AI agents call sources_remove to permanently remove resources in Adr Fpga Bootstrap, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why sources_remove is rated Critical

An AI agent that decides to call sources_remove doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Adr Fpga Bootstrap is gone. There is no undo for destructive operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs sources_remove safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Adr Fpga Bootstrap, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sources_remove, this is the rule to start with:

sources_remove Hidden

sources_remove is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

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

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about sources_remove

What does the sources_remove tool do? +

Remove files from the open project without deleting them from disk. It is categorised as a Destructive tool in the Adr Fpga Bootstrap 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 sources_remove? +

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

What risk level is sources_remove? +

sources_remove 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 sources_remove? +

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

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

sources_remove is provided by the Adr Fpga Bootstrap MCP server (zxyyz/adr-fpga-bootstrap). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Adr Fpga Bootstrap, and thousands of servers like it.

This server

All 39 Adr Fpga Bootstrap tools → Critical-risk tools on this server →

Across the catalogue

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →