create_template_variables

WHAT IT DOES

What create_template_variables does on HPE Aruba Networking Central MCP Server

AI agents use create_template_variables to create or update resources in HPE Aruba Networking Central MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your HPE Aruba Networking Central MCP Server environment.

WHY IT NEEDS A POLICY

Why create_template_variables needs a policy

This tool creates new template variables, which is a reversible write operation that modifies device configuration state. It does not delete data (not Destructive), execute arbitrary code (not Execute), move money (not Financial), or merely retrieve data (not Read).

From the tool's definition Tool name 'create_template_variables' and description 'Create template variables for a device' indicate this tool creates/modifies configuration data on a device.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_template_variables Rate-limited

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

View as policy code

policy.json

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

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches HPE Aruba Networking Central MCP Server, so you can run agents against it safely.

FAQ

Questions about create_template_variables

What does the create_template_variables tool do? +

Create template variables for a device. It is categorised as a Write tool in the HPE Aruba Networking Central MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_template_variables? +

Register the HPE Aruba Networking Central MCP Server MCP server in PolicyLayer and add a rule for create_template_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 HPE Aruba Networking Central MCP Server. Nothing to install.

What risk level is create_template_variables? +

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

Can I rate-limit create_template_variables? +

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

How do I block create_template_variables completely? +

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

What MCP server provides create_template_variables? +

create_template_variables is provided by the HPE Aruba Networking Central MCP Server MCP server (the-otner/aruba-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.