AI agents use create_matlab_script to create or update resources in MATLAB MCP Tool — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MATLAB MCP Tool environment.
This tool creates new files, which is a reversible write operation. While it doesn't execute code or cause destructive changes, it modifies the filesystem state. The severity is medium because an agent could create malicious scripts or fill disk space, but the effects are recoverable through file deletion. Confidence is high because the description unambiguously describes a creation operation.
From the tool's definition Tool description states 'Create a new MATLAB script file', which is a file creation operation that modifies the filesystem. The name 'create_matlab_script' explicitly indicates a creation action.
Documented attack patterns abuse exactly the kind of access create_matlab_script gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MATLAB MCP Tool, and nothing reaches the server without passing your rules. This is the rule we recommend for create_matlab_script:
{
"version": "1",
"default": "deny",
"tools": {
"create_matlab_script": {
"limits": [
{
"counter": "create_matlab_script_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_matlab_script 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 a new MATLAB script file. It is categorised as a Write tool in the MATLAB MCP Tool MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MATLAB MCP Tool MCP server in PolicyLayer and add a rule for create_matlab_script: 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 MATLAB MCP Tool. Nothing to install.
create_matlab_script 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_matlab_script 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_matlab_script. 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_matlab_script is provided by the MATLAB MCP Tool MCP server (neuromechanist/matlab-mcp-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MATLAB MCP Tool, 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.
15 MATLAB MCP Tool tools catalogued and risk-classified — across an index of 43,000+ MCP servers.