AI agents call list_workspace_variables to retrieve information from MATLAB MCP Tool without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays the current state of MATLAB workspace variables. The name explicitly indicates a listing/querying action ('list_'), which is a read-only operation. No modification, deletion, or execution is indicated. Even though the description is empty, the tool name and context clearly establish this as a data retrieval function.
From the tool's definition Tool name 'list_workspace_variables' and server description indicating 'manage workspace variables' and 'capture generated plots'; listing/querying variables is a read operation with no side effects.
Documented attack patterns abuse exactly the kind of access list_workspace_variables 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 list_workspace_variables:
{
"version": "1",
"default": "deny",
"tools": {
"list_workspace_variables": {}
}
}list_workspace_variables is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
list_workspace_variables. It is categorised as a Read tool in the MATLAB MCP Tool MCP Server, which means it retrieves data without modifying state.
Register the MATLAB MCP Tool MCP server in PolicyLayer and add a rule for list_workspace_variables: 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.
list_workspace_variables is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_workspace_variables 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 list_workspace_variables. 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.
list_workspace_variables 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.