AI agents invoke call_matlab_function to trigger actions in MATLAB MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Calling a MATLAB function with arbitrary arguments constitutes code execution. MATLAB functions can perform file I/O, system calls, network operations, or any other side effect. The blast radius is high because a misused or malicious function call could affect the host system, exfiltrate data, or cause destructive outcomes.
From the tool's definition 'Call a MATLAB function with arguments' — directly invokes MATLAB functions with caller-supplied arguments, executing arbitrary MATLAB code
Documented attack patterns abuse exactly the kind of access call_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 call_matlab_function:
{
"version": "1",
"default": "deny",
"tools": {
"call_matlab_function": {
"limits": [
{
"counter": "call_matlab_function_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}call_matlab_function stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Call a MATLAB function with arguments. It is categorised as a Execute tool in the MATLAB MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MATLAB MCP Server MCP server in PolicyLayer and add a rule for call_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.
call_matlab_function is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the call_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 call_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.
call_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.