add_mpsk_registration · API-Central MCP: Risk & Policy

WHAT IT DOES

What add_mpsk_registration does on API-Central

AI agents use add_mpsk_registration 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 add_mpsk_registration needs a policy

This tool creates new MPSK (Multiple Pre-Shared Key) registrations which modifies network authentication credentials and access control settings. While reversible (can be deleted), it affects network security posture and access controls. Categorized as Write rather than Execute because it creates/registers data rather than executing arbitrary commands.

From the tool's definition Tool name 'add_mpsk_registration' and description 'Create a Named MPSK registration' explicitly indicate a create operation that modifies network security configurations (MPSK = Multiple Pre-Shared Keys, used for network access authentication).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_mpsk_registration Rate-limited

add_mpsk_registration 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": {
    "add_mpsk_registration": {
      "limits": [
        {
          "counter": "add_mpsk_registration_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 add_mpsk_registration

What does the add_mpsk_registration tool do? +

Create a Named MPSK registration. network = SSID; password_policy default "WORDS". 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 add_mpsk_registration? +

Register the API-Central MCP server in PolicyLayer and add a rule for add_mpsk_registration: 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 add_mpsk_registration? +

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

Can I rate-limit add_mpsk_registration? +

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

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

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