Remove dev fee share from a wallet.
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.
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
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.
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.
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.
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.
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.
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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →