create_static_tag · API-Central MCP: Risk & Policy

WHAT IT DOES

What create_static_tag does on API-Central

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

This is a Write operation as it creates new data (classification tags) that can be used in authorization policies. While it doesn't directly delete or execute code, creating authorization-related tags could have security implications if misused to assign inappropriate roles.

From the tool's definition Tool creates a static classification tag with auto-generated UUID, described as used 'to assign roles' in authorization policies. The verb 'create' and the function of assigning roles indicate data modification with potential authorization side effects.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_static_tag Rate-limited

create_static_tag 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_static_tag": {
      "limits": [
        {
          "counter": "create_static_tag_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 create_static_tag

What does the create_static_tag tool do? +

Create a static classification tag (UUID auto-generated). Used in authz policies to assign roles. 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 create_static_tag? +

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

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

Can I rate-limit create_static_tag? +

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

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

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