remove_struct_field

THE RISK

Critical Risk

Why remove_struct_field needs a policy

Removing a field from a structure is an irreversible modification — the field and its data definition are permanently deleted from the structure. This is a destructive write operation that cannot be undone without manually re-adding the field, placing it in the Destructive category. Severity is medium since it affects binary analysis metadata/type definitions rather than live production data.

From the tool's definition Remove a field from a structure by index

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

POLICY

How to control remove_struct_field

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

policy.json

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

remove_struct_field 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 Kawaiidra MCP — 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 Kawaiidra MCP tools

Destructive cache_clear Clear cached analysis results. Can clear all cache or filter by binary/project. Destructive clear_comments Clear all comments (EOL, PRE, POST, PLATE) within a function Destructive delete_data_type Delete a user-defined data type from the binary. Destructive delete_function Delete a function by address or name. Removes the function definition but not the underlyi Destructive delete_label Delete a label/symbol at a specific address. Execute run_script Execute arbitrary Jython code in the Ghidra scripting environment. Has access to currentPr Execute analyze_binary Import and analyze a binary file with Ghidra. Supports PE, ELF, Mach-O, and raw formats. Write add_enum_value Add a value to an existing enumeration.

All 94 Kawaiidra MCP 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 Kawaiidra MCP → 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 remove_struct_field

What does the remove_struct_field tool do? +

Remove a field from a structure by index. It is categorised as a Destructive tool in the Kawaiidra MCP 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_struct_field? +

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

What risk level is remove_struct_field? +

remove_struct_field 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_struct_field? +

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

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

remove_struct_field is provided by the Kawaiidra MCP server (wagonbomb/kawaiidra-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Kawaiidra MCP tool call.

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

CHECK YOUR STACK →