AI agents use create_matlab_function to create or update resources in MATLAB MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MATLAB MCP Server environment.
This tool creates new MATLAB function files, which is a Write operation as it creates data/code artifacts. Severity is medium because while file creation is reversible (files can be deleted), it could be used to inject malicious MATLAB code into the environment, and the effects depend on what code is subsequently written and executed.
From the tool's definition Tool description states it 'Create[s] a new MATLAB function file', which is a creation operation that modifies the filesystem and MATLAB environment reversibly.
Documented attack patterns abuse exactly the kind of access create_matlab_function gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MATLAB MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_matlab_function:
{
"version": "1",
"default": "deny",
"tools": {
"create_matlab_function": {
"limits": [
{
"counter": "create_matlab_function_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_matlab_function 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 function file. It is categorised as a Write tool in the MATLAB MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MATLAB MCP Server MCP server in PolicyLayer and add a rule for create_matlab_function: 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 Server. Nothing to install.
create_matlab_function 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_function 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_function. 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_function is provided by the MATLAB MCP Server MCP server (tsuchijo/matlab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 4 MATLAB MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4 MATLAB MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.