AI agents invoke execute_section_by_index to trigger actions in MATLAB MCP Tool. 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 executes code sections in MATLAB by index reference. Execution of user-supplied or attacker-controlled code sections can trigger arbitrary MATLAB operations (calculations, file I/O, external command invocation via MATLAB functions).
From the tool's definition Tool name 'execute_section_by_index' combined with sibling tool 'execute_section' and server description stating it 'Enables interactive MATLAB development by allowing users to execute scripts and specific code sections' via 'MATLAB Python Engine.' The…
Documented attack patterns abuse exactly the kind of access execute_section_by_index 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 execute_section_by_index:
{
"version": "1",
"default": "deny",
"tools": {
"execute_section_by_index": {
"limits": [
{
"counter": "execute_section_by_index_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} execute_section_by_index 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_section_by_index. It is categorised as a Execute tool in the MATLAB MCP Tool MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MATLAB MCP Tool MCP server in PolicyLayer and add a rule for execute_section_by_index: 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.
execute_section_by_index 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_section_by_index 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_section_by_index. 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_section_by_index 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.