Low Risk

get_available_arrays

Get a list of available arrays in the active source.

How to control get_available_arrays ↓

What get_available_arrays does on ParaView-MCP

AI agents call get_available_arrays to retrieve information from ParaView-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_available_arrays needs a policy

This tool retrieves metadata about arrays present in the active ParaView source without performing any computation, creation, deletion, or modification of data. It is a read-only operation that provides information for subsequent visualization operations. The low severity reflects minimal blast radius—an AI agent cannot misuse this to cause harm, only to gather information about available data structures.

From the tool's definition Tool name 'get_available_arrays' and description 'Get a list of available arrays in the active source' indicates a query/retrieval operation with no side effects or data modification.

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

How to control get_available_arrays

PolicyLayer is an MCP gateway — it sits between your AI agents and ParaView-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_available_arrays:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_available_arrays": {}
  }
}

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

  1. Create a free account and register ParaView-MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_available_arrays

What does the get_available_arrays tool do? +

Get a list of available arrays in the active source. It is categorised as a Read tool in the ParaView-MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_available_arrays? +

Register the ParaView- MCP server in PolicyLayer and add a rule for get_available_arrays: 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 ParaView-MCP. Nothing to install.

What risk level is get_available_arrays? +

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

Can I rate-limit get_available_arrays? +

Yes. Add a rate_limit block to the get_available_arrays 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_available_arrays completely? +

Set action: deny in the PolicyLayer policy for get_available_arrays. 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_available_arrays? +

get_available_arrays is provided by the ParaView- MCP server (llnl/paraview_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every ParaView-MCP tool call.

Start from ParaView-MCP, 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.

23 ParaView-MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.