update_submodel_element_value

THE RISK

Medium Risk

Why update_submodel_element_value needs a policy

The tool updates (modifies) a Submodel Element value, which is a reversible write operation. It does not delete data (would be Destructive) or execute arbitrary code (would be Execute). However, severity is high because updating asset administration data in an industrial/manufacturing context (BaSyx/Asset Administration Shell) could have significant downstream effects on systems relying on this data.

From the tool's definition Tool name 'update_submodel_element_value' indicates modification of data. Server description explicitly states 'full CRUD operations' including update capability via REST API.

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

POLICY

How to control update_submodel_element_value

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_submodel_element_value": {
      "limits": [
        {
          "counter": "update_submodel_element_value_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

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

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Aas tools

Destructive delete_shell delete_shell Destructive delete_submodel delete_submodel Destructive delete_submodel_element delete_submodel_element Destructive delete_submodel_ref delete_submodel_ref Write create_shell create_shell Write create_submodel create_submodel Write create_submodel_element create_submodel_element Write create_submodel_ref create_submodel_ref

All 25 Aas tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about update_submodel_element_value

What does the update_submodel_element_value tool do? +

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

How do I enforce a policy on update_submodel_element_value? +

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

What risk level is update_submodel_element_value? +

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

Can I rate-limit update_submodel_element_value? +

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

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

update_submodel_element_value is provided by the Aas MCP server (smartfactory-kl/aas-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Aas tool call.

Start from Aas, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →