remove_dev_share

Remove dev fee share from a wallet.

SERVERBasis MCP Server SOURCElaunch-on-basis/mcp-ts

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/launch-on-basis-mcp-ts/remove-dev-share.md

WHAT IT DOES

What remove_dev_share does on Basis MCP Server

AI agents call remove_dev_share to permanently remove resources in Basis MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why remove_dev_share is rated Critical

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

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs remove_dev_share safely

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

remove_dev_share Hidden

remove_dev_share 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": [
    "remove_dev_share"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about remove_dev_share

What does the remove_dev_share tool do? +

Remove dev fee share from a wallet. It is categorised as a Destructive tool in the Basis MCP Server 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 remove_dev_share? +

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

What risk level is remove_dev_share? +

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

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

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

remove_dev_share is provided by the Basis MCP Server MCP server (launch-on-basis/mcp-ts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Basis MCP Server, and thousands of servers like it.

This server

All 204 Basis MCP Server 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 →