AI agents use add_struct_field to create or update resources in Kawaiidra MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kawaiidra MCP environment.
This tool performs a create/modify operation on project metadata (structure definitions) within Ghidra. While it doesn't alter the actual binary or create external effects, it modifies the analysis state reversibly. It fits Write category as it updates project data without destructive or irreversible consequences.
From the tool's definition add_struct_field modifies an existing structure by adding a field to it. This is a reversible data modification operation that creates or alters structural metadata within a binary analysis project.
Documented attack patterns abuse exactly the kind of access add_struct_field gives an agent:
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 add_struct_field:
{
"version": "1",
"default": "deny",
"tools": {
"add_struct_field": {
"limits": [
{
"counter": "add_struct_field_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_struct_field stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Add a field to an existing structure. It is categorised as a Write tool in the Kawaiidra MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kawaiidra MCP server in PolicyLayer and add a rule for add_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.
add_struct_field is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_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.
Set action: deny in the PolicyLayer policy for add_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.
add_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.
Start from Kawaiidra MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
94 Kawaiidra MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.