push_aruba_device_profiles · API-Central MCP: Risk & Policy

WHAT IT DOES

What push_aruba_device_profiles does on API-Central

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

WHY IT NEEDS A POLICY

Why push_aruba_device_profiles needs a policy

The tool creates or ensures existence of device profiles at the library level. This is a Write operation because it modifies configuration state (creating profiles if they don't exist). The idempotent nature means repeated calls are safe, but the primary function is to establish/write profile configuration.

From the tool's definition Tool description states it will "Ensure the four standard Aruba LLDP device profiles exist at library level" — this is a create/modify operation that establishes configuration profiles.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

push_aruba_device_profiles Rate-limited

push_aruba_device_profiles 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": {
    "push_aruba_device_profiles": {
      "limits": [
        {
          "counter": "push_aruba_device_profiles_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 API-Central, so you can run agents against it safely.

FAQ

Questions about push_aruba_device_profiles

What does the push_aruba_device_profiles tool do? +

Ensure the four standard Aruba LLDP device profiles exist at library level (idempotent). It is categorised as a Write tool in the API-Central MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on push_aruba_device_profiles? +

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

What risk level is push_aruba_device_profiles? +

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

Can I rate-limit push_aruba_device_profiles? +

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

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

push_aruba_device_profiles is provided by the API-Central MCP server (secure-ssid/centralmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.