AI agents use create_data_var to create or update resources in BinAssistMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your BinAssistMCP environment.
This tool creates or adds data variables to a binary analysis project, which is a reversible modification of project metadata/state. It does not delete data (so not Destructive), does not execute arbitrary code or system commands (so not Execute), and does not involve financial transactions (so not Financial). The write category is appropriate for tools that create new entities within the analysis framework.
From the tool's definition Tool name 'create_data_var' suggests creation of a data variable in the binary analysis context. The 'create_' prefix indicates a write operation that modifies the binary project state (similar to sibling tools like 'batch_rename' and 'comments' which are…
Documented attack patterns abuse exactly the kind of access create_data_var gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and BinAssistMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for create_data_var:
{
"version": "1",
"default": "deny",
"tools": {
"create_data_var": {
"limits": [
{
"counter": "create_data_var_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_data_var 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.
create_data_var. It is categorised as a Write tool in the BinAssistMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the BinAssist MCP server in PolicyLayer and add a rule for create_data_var: 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 BinAssistMCP. Nothing to install.
create_data_var 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 create_data_var 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 create_data_var. 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.
create_data_var is provided by the BinAssist MCP server (symgraph/binassistmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 44 BinAssistMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
44 BinAssistMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.