get_workspace

THE RISK

Low Risk

Why get_workspace needs a policy

The tool queries and retrieves the state of workspace variables without side effects. It is informational only and does not create, modify, delete, or execute operations. This is a typical Read operation with minimal risk.

From the tool's definition Tool name is 'get_workspace' and description states 'Get current MATLAB workspace variables' — this is a retrieval operation with no modification, deletion, or execution of code.

Documented attack patterns abuse exactly the kind of access get_workspace gives an agent:

POLICY

How to control get_workspace

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 get_workspace:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_workspace": {}
  }
}

get_workspace is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register MATLAB MCP Tool — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MATLAB MCP Tool tools

Execute execute_script Execute MATLAB code and return results with plots. Execute execute_section execute_section Execute execute_section_by_index execute_section_by_index Execute execute_section_by_title execute_section_by_title Write create_matlab_script Create a new MATLAB script file. Read analyze_figure analyze_figure Read get_analysis_prompt get_analysis_prompt Read get_figure_metadata get_figure_metadata

All 15 MATLAB MCP Tool tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_workspace

What does the get_workspace tool do? +

Get current MATLAB workspace variables. It is categorised as a Read tool in the MATLAB MCP Tool MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_workspace? +

Register the MATLAB MCP Tool MCP server in PolicyLayer and add a rule for get_workspace: 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.

What risk level is get_workspace? +

get_workspace is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_workspace? +

Yes. Add a rate_limit block to the get_workspace 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.

How do I block get_workspace completely? +

Set action: deny in the PolicyLayer policy for get_workspace. 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.

What MCP server provides get_workspace? +

get_workspace 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.

Enforce policy on every MATLAB MCP Tool tool call.

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.

CHECK YOUR STACK →