create_static_tag
Create a static classification tag (UUID auto-generated). Used in authz policies to assign roles.
This record as markdown: /tools/secure-ssid-centralmcp/create-static-tag.md
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 create_static_tag is rated Medium
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
The rule that runs create_static_tag safely
PolicyLayer is an MCP gateway: it sits between your AI agents and API-Central, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_static_tag, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect API-Central, apply this rule, and every create_static_tag call is checked against it from then on.
Questions about create_static_tag
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.
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.
create_static_tag is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
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.
More on API-Central, and thousands of servers like it.
This server
Across the catalogue