Execute a MATLAB script and return results.
AI agents invoke execute_matlab_script 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.
This tool runs arbitrary MATLAB code whose effects depend entirely on the script contents provided by the user/agent. While not inherently destructive (Write/Destructive require irreversibility; this is reversible depending on script logic), execution of arbitrary scripts is a classic Execute category risk.
From the tool's definition Tool name 'execute_matlab_script' combined with description 'Execute a MATLAB script and return results' directly indicates execution of arbitrary code.
Documented attack patterns abuse exactly the kind of access execute_matlab_script 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 execute_matlab_script:
{
"version": "1",
"default": "deny",
"tools": {
"execute_matlab_script": {
"limits": [
{
"counter": "execute_matlab_script_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}execute_matlab_script 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.
Execute a MATLAB script and return results. 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 execute_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 Server. Nothing to install.
execute_matlab_script 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 execute_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 execute_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.
execute_matlab_script 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.