remove_import_name · Ast Editor MCP: Risk & Policy

WHAT IT DOES

What remove_import_name does on Ast Editor

AI agents call remove_import_name to permanently remove resources in Ast Editor — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

WHY IT NEEDS A POLICY

Why remove_import_name needs a policy

Removing an import name from source code is a destructive, irreversible edit (without version control). The 'remove' prefix consistently indicates deletion across this server's toolset (cf. 'delete_in_body', 'delete_key'). The description is empty, lowering confidence slightly, but the naming pattern and server context make Destructive the most appropriate category.

From the tool's definition Tool name 'remove_import_name' combined with server context of 'surgical tools for structural edits' — 'remove' prefix strongly implies irreversible deletion of an import name from source code.

Attacks that exploit this kind of access

Questions about remove_import_name

What does the remove_import_name tool do? +

remove_import_name. It is categorised as a Destructive tool in the Ast Editor 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_import_name? +

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

What risk level is remove_import_name? +

remove_import_name 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_import_name? +

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

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

remove_import_name is provided by the Ast Editor MCP server (kambleakash0/ast-editor). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.