Medium Risk

iscsi_portal_update

Update an iSCSI portal

How to control iscsi_portal_update ↓

What iscsi_portal_update does on Truenas

AI agents use iscsi_portal_update to create or update resources in Truenas — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Truenas environment.

Medium Risk

Why iscsi_portal_update needs a policy

This tool modifies iSCSI portal configuration (a network-accessible storage protocol endpoint). While reversible (category: Write rather than Destructive), iSCSI portal configuration changes can have significant impact on network accessibility, authentication, and storage service availability.

From the tool's definition Tool name is 'iscsi_portal_update' with description 'Update an iSCSI portal'. The verb 'update' indicates modification of an existing iSCSI portal configuration, which is a reversible write operation on network/storage infrastructure settings.

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

How to control iscsi_portal_update

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "iscsi_portal_update": {
      "limits": [
        {
          "counter": "iscsi_portal_update_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

iscsi_portal_update stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Truenas — 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.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about iscsi_portal_update

What does the iscsi_portal_update tool do? +

Update an iSCSI portal. It is categorised as a Write tool in the Truenas MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on iscsi_portal_update? +

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

What risk level is iscsi_portal_update? +

iscsi_portal_update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit iscsi_portal_update? +

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

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

iscsi_portal_update is provided by the Truenas MCP server (spranab/truenas-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Truenas tool call.

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

279 Truenas 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.