# apstra_set_application_point_assignment

A write tool on the API-Central MCP server.

Agent View of the PolicyLayer registry record for `apstra_set_application_point_assignment`. HTML page: https://policylayer.com/tools/secure-ssid-centralmcp/apstra-set-application-point-assignment

## Facts

- Tool: `apstra_set_application_point_assignment`
- Server: API-Central (`secure-ssid/centralmcp`) — https://policylayer.com/tools/secure-ssid-centralmcp.md
- Homepage: https://github.com/secure-ssid/centralmcp
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "apstra_set_application_point_assignment",
    "arguments": {}
  }
}
```

## Why apstra_set_application_point_assignment is rated Medium

The verb 'set' indicates a write/modification operation. Application point assignments in network infrastructure control how traffic is routed and processed, making unauthorized changes potentially disruptive to network operations. However, without explicit deletion, data corruption, or permanent infrastructure damage in the name, this is classified as Write rather than Destructive.

From the tool's own definition: "Tool name 'apstra_set_application_point_assignment' indicates a setter operation that modifies application point assignments in Aruba's Apstra infrastructure. The 'set_' prefix strongly suggests state modification. Description is empty, limiting certainty."

## Use case

AI agents use apstra_set_application_point_assignment 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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches API-Central:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "apstra_set_application_point_assignment": {
      "limits": [
        {
          "counter": "apstra_set_application_point_assignment_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on API-Central (589)

- `aos8_execute_migration_rollback` — Destructive — https://policylayer.com/tools/secure-ssid-centralmcp/aos8-execute-migration-rollback.md
- `aos8_logout` — Destructive — https://policylayer.com/tools/secure-ssid-centralmcp/aos8-logout.md
- `apstra_delete_connectivity_template` — Destructive — https://policylayer.com/tools/secure-ssid-centralmcp/apstra-delete-connectivity-template.md
- `clear_alerts` — Destructive — https://policylayer.com/tools/secure-ssid-centralmcp/clear-alerts.md
- `clearpass_delete_endpoint` — Destructive — https://policylayer.com/tools/secure-ssid-centralmcp/clearpass-delete-endpoint.md
- `clearpass_delete_guest` — Destructive — https://policylayer.com/tools/secure-ssid-centralmcp/clearpass-delete-guest.md
- `delete_aaa_profile` — Destructive — https://policylayer.com/tools/secure-ssid-centralmcp/delete-aaa-profile.md
- `delete_auth_profile` — Destructive — https://policylayer.com/tools/secure-ssid-centralmcp/delete-auth-profile.md
- `delete_auth_server` — Destructive — https://policylayer.com/tools/secure-ssid-centralmcp/delete-auth-server.md
- `delete_authz_policy` — Destructive — https://policylayer.com/tools/secure-ssid-centralmcp/delete-authz-policy.md
- `delete_config_assignment` — Destructive — https://policylayer.com/tools/secure-ssid-centralmcp/delete-config-assignment.md
- `delete_device_groups` — Destructive — https://policylayer.com/tools/secure-ssid-centralmcp/delete-device-groups.md
- `delete_device_notes` — Destructive — https://policylayer.com/tools/secure-ssid-centralmcp/delete-device-notes.md
- `delete_glp_role_assignment` — Destructive — https://policylayer.com/tools/secure-ssid-centralmcp/delete-glp-role-assignment.md
- `delete_glp_scope_group` — Destructive — https://policylayer.com/tools/secure-ssid-centralmcp/delete-glp-scope-group.md
- `delete_glp_scope_group_scopes` — Destructive — https://policylayer.com/tools/secure-ssid-centralmcp/delete-glp-scope-group-scopes.md
- `delete_gw_policy` — Destructive — https://policylayer.com/tools/secure-ssid-centralmcp/delete-gw-policy.md
- `delete_mac_registration` — Destructive — https://policylayer.com/tools/secure-ssid-centralmcp/delete-mac-registration.md
- `delete_mpsk_registration` — Destructive — https://policylayer.com/tools/secure-ssid-centralmcp/delete-mpsk-registration.md
- `delete_network_profile` — Destructive — https://policylayer.com/tools/secure-ssid-centralmcp/delete-network-profile.md
- `delete_notification_rule` — Destructive — https://policylayer.com/tools/secure-ssid-centralmcp/delete-notification-rule.md
- `delete_overlay_ssid` — Destructive — https://policylayer.com/tools/secure-ssid-centralmcp/delete-overlay-ssid.md
- `delete_report` — Destructive — https://policylayer.com/tools/secure-ssid-centralmcp/delete-report.md
- `delete_report_run` — Destructive — https://policylayer.com/tools/secure-ssid-centralmcp/delete-report-run.md
- `delete_role` — Destructive — https://policylayer.com/tools/secure-ssid-centralmcp/delete-role.md
- `delete_role_acl` — Destructive — https://policylayer.com/tools/secure-ssid-centralmcp/delete-role-acl.md
- `delete_server_group` — Destructive — https://policylayer.com/tools/secure-ssid-centralmcp/delete-server-group.md
- `delete_site_collections_bulk` — Destructive — https://policylayer.com/tools/secure-ssid-centralmcp/delete-site-collections-bulk.md
- `delete_sites_bulk` — Destructive — https://policylayer.com/tools/secure-ssid-centralmcp/delete-sites-bulk.md
- `delete_static_tag` — Destructive — https://policylayer.com/tools/secure-ssid-centralmcp/delete-static-tag.md
- …and 559 more: https://policylayer.com/tools/secure-ssid-centralmcp.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=secure-ssid-centralmcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/secure-ssid-centralmcp