export_model
AI agents use export_model to create or update resources in GameDevBench MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GameDevBench MCP environment.
Export operations are Write actions—they create output files or representations of data, which are reversible (files can be deleted or replaced). While export could theoretically involve destructive overwrites if the destination is not handled safely, the primary action is data creation/serialization rather than irreversible deletion.
From the tool's definition Tool name is 'export_model' within a Godot game development benchmarking context; the description is empty, limiting direct evidence.
Attacks that exploit this kind of access
export_model. It is categorised as a Write tool in the GameDevBench MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GameDevBench MCP server in PolicyLayer and add a rule for export_model: 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 GameDevBench MCP. Nothing to install.
export_model 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 export_model 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 export_model. 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.
export_model is provided by the GameDevBench MCP server (seeleai/gamedevbench-mcp). 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 →